From: David Ahern <dsahern@gmail.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@vger.kernel.org, viro@ZenIV.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: NULL pointer dereference in autofs4_expire_wait
Date: Fri, 11 Oct 2013 07:29:24 -0600 [thread overview]
Message-ID: <5257FD34.2060406@gmail.com> (raw)
In-Reply-To: <1381485327.2631.18.camel@perseus.fritz.box>
On 10/11/13 3:55 AM, Ian Kent wrote:
> On Fri, 2013-10-11 at 10:06 +0800, Ian Kent wrote:
>> On Thu, 2013-10-10 at 17:22 -0600, David Ahern wrote:
>>> Running 3.12-rc3 just hit BUG in autofs4_expire_wait
>>
>> It doesn't look like this could be due to Al's change to the locking in
>> autos4_wait() and that the only change to autofs that I'm aware of.
>>
>> Could you do a bisect please?
>
> Of course that assumes it's repeatable.
> Is it?
>
> Can you provide any information about the environment and activity that
> was happening at the time of the BUG()?
The system was up and running for 9 days before hitting the BUG. After
that with 3 cpus on softlockup I had to do a reboot (forced). After the
reboot I continued the workload again without a repeat incident (yet),
so I am not sure bisect is going to be possible.
This is a corporate environment where practically everything is in an
automount. Specific to this problem I was repeatedly building a
workspace in one window, using cscope in another and checking code
against a different workspace in a third -- all 3 of those were
different automounts and different NAS servers.
From objdump on vmlinux the line in question is fs/autofs4/expire.c:465
if (ino->flags & AUTOFS_INF_EXPIRING) {
I will be continuing the sequence above today (working through compile
problems for on OS port). I will bump the kernel to top of tree and see
if it repeats.
David
next prev parent reply other threads:[~2013-10-11 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 23:22 NULL pointer dereference in autofs4_expire_wait David Ahern
2013-10-11 2:06 ` Ian Kent
2013-10-11 9:55 ` Ian Kent
2013-10-11 13:29 ` David Ahern [this message]
2013-10-12 1:56 ` Ian Kent
2013-10-13 20:13 ` David Ahern
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=5257FD34.2060406@gmail.com \
--to=dsahern@gmail.com \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@ZenIV.linux.org.uk \
/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.