On Mon, 28 Aug 2006 08:52:02 -0700
"Miles Lane" <[EMAIL PROTECTED]> wrote:

> On 8/27/06, David Miller <[EMAIL PROTECTED]> wrote:
> > From: Andrew Morton <[EMAIL PROTECTED]>
> > Date: Sun, 27 Aug 2006 00:19:43 -0700
> >
> > > Jeremy reported that a while back too.  I do not know what is causing it
> > > and as far as I know no net developers have yet looked into it.
> >
> > A debugging patch like this one should help figure out the culprit.
> >
> > If we don't see the gibberish netdevice name printed in the kernel
> > logs, then likely something is corrupting the netdevice structure or
> > the memory holding the name.
> >
> > diff --git a/net/core/dev.c b/net/core/dev.c
> > index d4a1ec3..45f9b19 100644
> > --- a/net/core/dev.c
> > +++ b/net/core/dev.c
> > @@ -738,6 +738,11 @@ int dev_change_name(struct net_device *d
> >
> >         if (!dev_valid_name(newname))
> >                 return -EINVAL;
> > +#if 1
> > +       printk("[%s:%d]: Changing netdevice name from [%s] to [%s]\n",
> > +              current->comm, current->pid,
> > +              dev->name, newname);
> > +#endif
> >
> >         if (strchr(newname, '%')) {
> >                 err = dev_alloc_name(dev, newname);
> >
> 
> Dan, do you have any idea why NetworkManager from Ubuntu 6.06.1
> would be corrupting network device names on recent MM kernels?
> I haven't seen this happening with Ubuntu's kernels.  If you like, I can
> send you my kernel .config file.
> 
> Here's what I get:
> 

grepping for `ioctl' gives:

ioctl(9, SIOCGIWNAME, 0xbfe38d8c)                 = -1 EINVAL (Invalid argument)
ioctl(9, SIOCETHTOOL, 0xbfe38d2c)                 = 0
ioctl(11, SIOCGIFHWADDR, {ifr_name="eth0", ???})  = -1 ENODEV (No such device)
ioctl(11, SIOCGIFFLAGS, {ifr_name="eth0", ???})   = -1 ENODEV (No such device)

Perhaps you could generate the strace output for 2.6.18-rc5, grep that for
ioctl, look for differences?  That initial SIOCGIWNAME failure is fishy.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to