1 May 2011 06:47
Re: [patch net-next-2.6] net: call dev_alloc_name from register_netdevice
Stephen Hemminger <shemminger <at> vyatta.com>
2011-05-01 04:47:35 GMT
2011-05-01 04:47:35 GMT
On Sat, 30 Apr 2011 22:57:52 +0200 Jiri Pirko <jpirko <at> redhat.com> wrote: > Sat, Apr 30, 2011 at 07:34:44PM CEST, shemminger <at> vyatta.com wrote: > >On Sat, 30 Apr 2011 13:21:32 +0200 > >Jiri Pirko <jpirko <at> redhat.com> wrote: > > > >> Force dev_alloc_name() to be called from register_netdevice() by > >> dev_get_valid_name(). That allows to remove multiple explicit > >> dev_alloc_name() calls. > >> > >> The possibility to call dev_alloc_name in advance remains. > >> > >> This also fixes veth creation regresion caused by > >> 84c49d8c3e4abefb0a41a77b25aa37ebe8d6b743 > >> > >> Signed-off-by: Jiri Pirko <jpirko <at> redhat.com> > > > >The problem with this then you have to audit all the calls > >to register_netdevice to make sure that user can't provide a bad > >value which then is passed a format string. Why not just fix > >just veth which would be safer. > > Well it looks convenient to do name allocations inside > register_netdevice generically. For special cases dev_get_valid_name() > can be still used as before (this I think should be also prohibited in > future). > > Also I think that drivers should be responsible for what they are > passing from user to core. Btw could you please give me an example of(Continue reading)
RSS Feed