linux-kernel - Re: cannot set IP for ethernet

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Jun 2007 13:21:29 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	linux-kernel@...r.kernel.org,
	Linux Netdev List <netdev@...r.kernel.org>,
	Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: cannot set IP for ethernet

Am Mittwoch, 13. Juni 2007 schrieb Patrick McHardy:
> Oliver Neukum wrote:
> > Am Dienstag, 12. Juni 2007 schrieb Patrick McHardy:
> > 
> >>Oliver Neukum wrote:
> >>
> >>>with 2.6.22-rc4-git2 I am getting errors when setting IP for ethernet
> >>>interfaces:
> >>>
> >>>ioctl(4, SIOCSIFADDR, 0x7fff94931600)   = -1 ENOBUFS (No buffer space available)
> >>>
> >>>The error is independant of the interface. It happens to all interfaces.
> >>>There's nothing in the syslog.
> >>>
> >>>valisk:/home/oliver # uname -a
> >>>Linux valisk 2.6.22-rc4-git2-default #3 SMP Tue Jun 12 13:27:54 CEST 2007 x86_64 x86_64 x86_64 GNU/Linux
> >>
> >>
> >>This can happen if the initial inetdev allocation when the netdevice is
> >>registered fails. I think it would make sense to try to allocate again
> >>when adding addresses in that case, otherwise there is no way of
> >>recovery other than unregistering and registering the device again.
> > 
> > 
> > With your patch the problem has gone away. Is there a way to especially
> > stress the system in that regard?
> 
> 
> Its a failed allocation at NETDEV_REGISTER time. I guess you could
> keep unloading + reloading the driver module to try to reproduce it.

If that is the cause, why doesn't it strike from the very beginning? How
come it fails after some time?

	Regards
		Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/