From: Oliver Neukum <oliver@neukum.org>
To: Patrick McHardy <kaber@trash.net>
Cc: linux-kernel@vger.kernel.org,
Linux Netdev List <netdev@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: cannot set IP for ethernet
Date: Wed, 13 Jun 2007 13:55:27 +0200 [thread overview]
Message-ID: <200706131355.27574.oliver@neukum.org> (raw)
In-Reply-To: <466FD439.2040807@trash.net>
Am Mittwoch, 13. Juni 2007 schrieb Patrick McHardy:
> Oliver Neukum wrote:
> > Am Mittwoch, 13. Juni 2007 schrieb Patrick McHardy:
> >>>>
> >>>>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?
>
>
> It might also be a failed in_ifaddr allocation. In that case my patch
> shouldn't help though.
The problem is that I don't know how to provoke the failure. I might
be doing another workload today than yesterday. Perhaps I should
do several compilations like yesterday?
Regards
Oliver
next prev parent reply other threads:[~2007-06-13 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706121441.13561.oliver@neukum.org>
2007-06-12 14:06 ` cannot set IP for ethernet Patrick McHardy
2007-06-13 8:39 ` Oliver Neukum
2007-06-13 11:14 ` Patrick McHardy
2007-06-13 11:21 ` Oliver Neukum
2007-06-13 11:25 ` Patrick McHardy
2007-06-13 11:55 ` Oliver Neukum [this message]
2007-06-14 3:53 ` Herbert Xu
2007-06-14 3:56 ` David Miller
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=200706131355.27574.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).