From: Stijn Devriendt <highguy@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: Oops in d_instantiate (fs/cache.c)
Date: Mon, 12 Dec 2011 12:35:52 +0100 [thread overview]
Message-ID: <CAOY=C6GeaqnAOyYgt18xwV3KafHjMA_8QZQBqXEoXox4eNXPwA@mail.gmail.com> (raw)
In-Reply-To: <CAOY=C6HuVEYpkap3dVmgmC7d+SDhvO-zc79RvCvkZCham3MiXg@mail.gmail.com>
On Sat, Dec 3, 2011 at 1:19 PM, Stijn Devriendt <highguy@gmail.com> wrote:
> Hi all,
>
> I've had 2 occasions where udev crashed during bootup.
> The second time carried a kernel log where the following line
> "BUG_ON(!list_empty(&entry->d_alias))"
> in d_instantiate is triggered when udev is attempting to
> create a symlink in /dev (which is tmpfs/shmem).
>
> I've tried reproducing this by doing as udev does:
> - create temporary symlink
> - move temporary symlink into place
> in a tight loop (multiple processes) while multiple
> other processes were removing the symlink in a
> tight loop.
> A third script was flushing the dentry/inode cache
> every so often using drop_caches.
> All to no avail.
>
> I've been digging around in the kernel sources,
> but I'm not sure what the d_alias field means
> and what the actual case is the BUG_ON is
> meant to catch. I'd like to be able to find a way
> to reproduce this, because so far it's happened only
> twice in 2 weeks over multiple systems doing
> many reboots in a testing setup.
> Can someone explain this to me in short?
>
> Thanks,
> Stijn
Trying resend...
Stijn
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-12-12 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 12:19 Stijn Devriendt
2011-12-12 11:35 ` Stijn Devriendt [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='CAOY=C6GeaqnAOyYgt18xwV3KafHjMA_8QZQBqXEoXox4eNXPwA@mail.gmail.com' \
--to=highguy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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