From: Kees Bakker <spam@tasking.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/lockd/mon.c:150, was Re: [PATCH v2 3/3] lockd: create and ...
Date: Fri, 02 Nov 2012 08:50:03 +0100 [thread overview]
Message-ID: <47e3.50937b2c.27859@altium.nl> (raw)
In-Reply-To: <508FD068.2000903@tasking.nl>
On 30-10-12 14:04, Kees Bakker wrote:
> On 18-09-12 11:37, Stanislav Kinsbursky wrote:
>> NSM RPC client can be required on NFSv3 umount, when child reaper is dying
>> (and destroying it's mount namespace). It means, that current nsproxy is set
>> to NULL already, but creation of RPC client requires UTS namespace for gaining
>> hostname string.
>>
>> This patch creates reference-counted per-net NSM client on first monitor
>> request and destroys it after last unmonitor request.
>>
>
> We're hitting the BUG_ON that was added in this patch. I've tried it with
> 3.6.3 and 3.6.4
>
> It happens almost immediate when I do apt-get update (the archive is on NFS).
To follow up (just talking to myself I guess), stable v3.6.5 solves the problem,
thanks. I did try v3.6.4 first but the patch inthere was not sufficient.
--
Kees
prev parent reply other threads:[~2012-11-02 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 9:37 [PATCH v2 0/3] lockd: use per-net refrence-counted NSM clients Stanislav Kinsbursky
2012-09-18 9:37 ` [PATCH v2 1/3] lockd: per-net NSM client creation and destruction helpers introduced Stanislav Kinsbursky
2012-09-18 9:37 ` [PATCH v2 2/3] lockd: use rpc client's cl_nodename for id encoding Stanislav Kinsbursky
2012-09-18 9:37 ` [PATCH v2 3/3] lockd: create and use per-net NSM RPC clients on MON/UNMON requests Stanislav Kinsbursky
2012-10-30 13:04 ` kernel BUG at fs/lockd/mon.c:150, was Re: [PATCH v2 3/3] lockd: create and Kees Bakker
2012-10-30 13:23 ` Kees Bakker
2012-11-02 7:50 ` Kees Bakker [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=47e3.50937b2c.27859@altium.nl \
--to=spam@tasking.nl \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.