public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] musl: fix conflict on ethhdr definition
Date: Wed, 27 Nov 2024 15:55:00 +0100	[thread overview]
Message-ID: <d245f0e5-2299-4ef0-98d0-0dd7e6636eed@redhat.com> (raw)
In-Reply-To: <20241127154809.2a49f2f8@elisabeth>

On 27/11/2024 15:48, Stefano Brivio wrote:
> On Wed, 27 Nov 2024 15:41:30 +0100
> Laurent Vivier <lvivier@redhat.com> wrote:
> 
>> there is a conflict between netinet/if_ether.h provided by musl and
>> linux/if_ether.h provided by the linux headers:
>>
>>    In file included from passt.h:185,
>>                     from tcp_vu.c:21:
>>    /usr/include/netinet/if_ether.h:115:8: error: redefinition of 'struct ethhdr'
>>      115 | struct ethhdr {
>>          |        ^~~~~~
>>    In file included from /usr/include/linux/virtio_net.h:32,
>>                     from tcp_vu.c:17:
>>    /usr/include/linux/if_ether.h:173:8: note: originally defined here
>>      173 | struct ethhdr {
>>          |        ^~~~~~
>>
>> The kernel headers provide a flag to disable the definition in this case,
>> __UAPI_DEF_ETHHDR (see /usr/include/linux/if_ether.h comment).
>>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> ---
>>   Makefile | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/Makefile b/Makefile
>> index cb7448079de5..2aa56ada65fd 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -33,6 +33,9 @@ FLAGS +=  $(FORTIFY_FLAG) -O2 -pie -fPIE
>>   FLAGS += -DPAGE_SIZE=$(shell getconf PAGE_SIZE)
>>   FLAGS += -DVERSION=\"$(VERSION)\"
>>   FLAGS += -DDUAL_STACK_SOCKETS=$(DUAL_STACK_SOCKETS)
>> +ifeq (musl, $(word 4,$(subst -, ,$(TARGET))))
>> +FLAGS += -D__UAPI_DEF_ETHHDR=0
>> +endif
> 
> Uh oh, I just solved this locally (I was about to push, but I stopped
> in time) by simply including <linux/if_ether.h> instead of
> <netinet/if_ether.h> from passt.h.
> 
> I'm not sure what's the best solution: mine is simpler, but I'm not
> really fond of including Linux-specific stuff if there's no need for
> it, so I'd slightly prefer yours.
> 
> On the other hand, it's not just for musl. If somebody tries to build
> this against, say, uClibc-ng (no reports about that yet), they will
> probably run into trouble as well.

In fact, in /usr/include/linux/if_ether.h they say:

/* allow libcs like musl to deactivate this, glibc does not implement this. */

So I think musl should set the value and then I found:

#define __UAPI_DEF_ETHHDR       0

in /usr/include/netinet/if_ether.h

So I think the solution is to include netinet/if_ether.h before linux/if_ether.h

> 
> Or should we just unconditionally #define __UAPI_DEF_ETHHDR=0 just
> before including <linux/virtio_net.h>?

If you do that, I think it will not work anymore with glibc

Thanks,
Laurent
> 


  reply	other threads:[~2024-11-27 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 14:41 [PATCH] musl: fix conflict on ethhdr definition Laurent Vivier
2024-11-27 14:48 ` Stefano Brivio
2024-11-27 14:55   ` Laurent Vivier [this message]
2024-11-27 15:05     ` Stefano Brivio
2024-11-27 15:37       ` Laurent Vivier
2024-11-27 15:45         ` Stefano Brivio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d245f0e5-2299-4ef0-98d0-0dd7e6636eed@redhat.com \
    --to=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).