From: Stephen Hemminger <shemminger@osdl.org>
To: David Miller <davem@davemloft.net>
Cc: yoshfuji@linux-ipv6.org, tgraf@suug.ch, netdev@vger.kernel.org,
usagi-core@linux-ipv6.org
Subject: Re: [GIT PATCH] NET: Fixes for net-2.6.19
Date: Thu, 28 Sep 2006 08:36:45 -0700 [thread overview]
Message-ID: <20060928083645.786b1ab1@freekitty> (raw)
In-Reply-To: <20060927.224444.109879330.davem@davemloft.net>
On Wed, 27 Sep 2006 22:44:44 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> Date: Tue, 19 Sep 2006 00:08:00 +0900 (JST)
>
> > [XFRM]: Do not add a state whose SPI is zero to the SPI hash.
> >
> > SPI=0 is used for acquired IPsec SA and MIPv6 RO state.
> > Such state should not be added to the SPI hash
> > because we do not care about it on deleting path.
> >
> > Signed-off-by: Masahide NAKAMURA <nakam@linux-ipv6.org>
> > Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
>
> Patch applied, thank you.
>
> But the rest of these patches need more thought about these header
> file issues.
>
> > [NET]: Move netlink interface bits to linux/if_link.h.
> >
> > Moving netlink interface bits to linux/if.h is rather troublesome for
> > applications including both linux/if.h (which was changed to be included
> > from linux/rtnetlink.h automatically) and net/if.h.
> >
> > Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
>
> If it is illegal for user to include kernel's linux/if.h (by any
> means) if he uses net/if.h from userland headers, then he should
> also avoid including the kernel's rtnetlink.h header too.
>
> I understand the issue, in that net/if.h defines macros that
> linux/if.h defines as well so there are conflicts (even though
> in the end the same exact values are used).
>
> What I see happening is that the troublesome interfaces move from
> linux/if.h to a new file named linux/if_addr.h, then this gets
> included again to linux/rtnetlink.h but only for userspace with
> some messy ifdefs.
>
> These kinds of things don't go away, they stay around forever once
> you decide to support them.
>
> Actually, what I'm going to do is apply:
>
> [NET]: Move netlink interface bits to linux/if_link.h.
> [NET] KBUILD: Add missing entries for new net headers.
>
> And leave the rest for now.
>
Please figure out how to keep rtnetlink.h useful from user space.
I tried putting the current sanitized version of rtnetlink.h into
iproute2 and the build fails.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-09-28 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 15:08 [GIT PATCH] NET: Fixes for net-2.6.19 YOSHIFUJI Hideaki / 吉藤英明
2006-09-18 18:57 ` Thomas Graf
2006-09-21 5:30 ` YOSHIFUJI Hideaki / 吉藤英明
2006-09-21 10:14 ` Thomas Graf
2006-09-28 5:44 ` David Miller
2006-09-28 15:36 ` Stephen Hemminger [this message]
2006-09-28 21:33 ` David Miller
2006-09-28 22:50 ` Stephen Hemminger
2006-09-28 23:04 ` David Miller
2006-09-28 23:27 ` Stephen Hemminger
2006-09-29 0:28 ` David Miller
2006-09-29 1:59 ` Masahide NAKAMURA
2006-09-30 7:27 ` [IPROUTE2][PATCH] Add missing macros which was removed from kernel header. (Re: [GIT PATCH] NET: Fixes for net-2.6.19) Masahide NAKAMURA
2006-10-05 18:01 ` Stephen Hemminger
2006-10-09 16:08 ` [GIT PATCH] NET: Fixes for net-2.6.19 Stephen Hemminger
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=20060928083645.786b1ab1@freekitty \
--to=shemminger@osdl.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=usagi-core@linux-ipv6.org \
--cc=yoshfuji@linux-ipv6.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox