From: David Miller <davem@davemloft.net>
To: dwmw2@infradead.org
Cc: sjurbren@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] Fix caif BUG() with network namespaces
Date: Tue, 25 Oct 2011 19:22:59 -0400 (EDT) [thread overview]
Message-ID: <20111025.192259.258695838207862829.davem@davemloft.net> (raw)
In-Reply-To: <1319527522.24797.10.camel@shinybook.infradead.org>
From: David Woodhouse <dwmw2@infradead.org>
Date: Tue, 25 Oct 2011 09:25:21 +0200
> The caif code will register its own pernet_operations, and then register
> a netdevice_notifier. Each time the netdevice_notifier is triggered,
> it'll do some stuff... including a lookup of its own pernet stuff with
> net_generic().
>
> If the net_generic() call ever returns NULL, the caif code will BUG().
> That doesn't seem *so* unreasonable, I suppose — it does seem like it
> should never happen.
>
> However, it *does* happen. When we clone a network namespace,
> setup_net() runs through all the pernet_operations one at a time. It
> gets to loopback before it gets to caif. And loopback_net_init()
> registers a netdevice... while caif hasn't been initialised. So the caif
> netdevice notifier triggers, and immediately goes BUG().
>
> We could imagine a complex and overengineered solution to this generic
> class of problems, but this patch takes the simple approach. It just
> makes caif_device_notify() *not* go looking for its pernet data
> structures if the device it's being notified about isn't a caif device
> in the first place.
>
> Cc: stable@kernel.org
> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
> Acked-by: Sjur Brændeland <sjur.brandeland@stericsson.com>
Applied, thanks.
prev parent reply other threads:[~2011-10-25 23:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 20:51 caif BUG() with network namespaces Woodhouse, David
2011-10-21 21:55 ` Sjur Brændeland
2011-10-23 21:21 ` [PATCH] Fix " Woodhouse, David
2011-10-23 21:24 ` [non-quoted-printable PATCH] " Woodhouse, David
2011-10-24 15:51 ` Sjur Brændeland
2011-10-24 22:28 ` David Miller
2011-10-25 7:25 ` [PATCH] " David Woodhouse
2011-10-25 23:22 ` David Miller [this message]
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=20111025.192259.258695838207862829.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=netdev@vger.kernel.org \
--cc=sjurbren@gmail.com \
/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).