From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: kernel BUG at include/net/netns/generic.h:41
Date: Thu, 05 Apr 2012 20:08:31 +0400 [thread overview]
Message-ID: <4F7DC37F.7090404@parallels.com> (raw)
In-Reply-To: <1333390230.13718.34.camel@lade.trondhjem.org>
02.04.2012 22:10, Myklebust, Trond пишет:
> This looks related to the recent net namespace changes, so I'm adding
> Stanislav.
>
Hi, Trond.
Looks like we stepped into exactly that situation, what Al Viro was talking on
LFS about early registering of file system before other module "init" operations
completed.
I.e. SUNRPC registers it's file system, and then we have races between
register_pernet_subsys() call and mount of SUNRPC PipeFS.
BTW, these races can be triggered only if mount of SUNRPC PipeFS is called prior
to SUNRPC module insertion is completed. In spite of it, I'll send the patch soon.
But I'm not 100% sure, that this patch will solve Dave's problem.
So, there are few questions to you, Dave:
1) can this happen (PipeFS mount attempt before SUNPRC module insertion has
returned any value) in your case?
2) how often do you experience this problem? Not every boot, I suppose?
3) And is it easy for you to reproduce?
--
Best regards,
Stanislav Kinsbursky
next prev parent reply other threads:[~2012-04-05 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 0:23 kernel BUG at include/net/netns/generic.h:41 Dave Jones
2012-04-02 17:26 ` Dave Jones
2012-04-02 18:10 ` Myklebust, Trond
2012-04-05 12:21 ` Stanislav Kinsbursky
2012-04-05 16:08 ` Stanislav Kinsbursky [this message]
2012-04-05 16:12 ` Dave Jones
2012-04-05 16:14 ` Stanislav Kinsbursky
2012-04-25 22:58 ` Dave Jones
2012-04-26 6:25 ` Stanislav Kinsbursky
2012-04-26 12:02 ` Myklebust, Trond
2012-04-26 14:06 ` Dave Jones
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=4F7DC37F.7090404@parallels.com \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=davej@redhat.com \
--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