[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <82C9FC7ED59434458AD4E09AFF2DE230BF09EE@FIESEXC006.nsn-intra.net>
Date: Thu, 27 Oct 2011 10:20:46 +0300
From: "Vaittinen, Matti (EXT-Other - FI/Oulu)"
<matti.vaittinen.ext@....com>
To: "ext Stephen Hemminger" <stephen.hemminger@...tta.com>,
"David Miller" <davem@...emloft.net>
Cc: <netdev@...r.kernel.org>
Subject: RE: [PATCH] IPv6: NLM_F_* flag support for route creation/changing when using netlink.
> -----Original Message-----
> From: ext Stephen Hemminger [mailto:stephen.hemminger@...tta.com]
> Sent: Thursday, October 27, 2011 10:12 AM
> To: David Miller
> Cc: netdev@...r.kernel.org; Vaittinen, Matti (EXT-Other - FI/Oulu)
> Subject: Re: [PATCH] IPv6: NLM_F_* flag support for route
creation/changing when using netlink.
>
>
> > From: "Vaittinen, Matti (EXT-Other - FI/Oulu)"
> > <matti.vaittinen.ext@....com>
> > Date: Thu, 27 Oct 2011 09:26:05 +0300
> >
> > >
> > > Will requiring NLM_F_CREATE break lots of existing userspace
> > > software?
> >
> > I can almost guarenetee that since we haven't been requiring this,
it
> > will break almost everything.
>
> Why not just make it a kernel warning for several releases.
>
> Just checked, and iproute and quagga will have no problem since they
both already pass the CREATE flag.
For me kernel warning sounds like a reasonable approach. I will change
the patch to not drop the request with error, but to issue a warning
instead. I'll also try using better email client next time.
Furthermore I believe that most tools used for both IPv4 and IPv6
routing (like iproute) do add the CREATE flag because IPv4 route
creation does require it.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists