From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 51391] BUG: unable to handle kernel NULL pointer dereference
Date: Mon, 11 Feb 2013 10:04:51 +0000 (UTC) [thread overview]
Message-ID: <20130211100451.D64AC11FF22@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-51391-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=51391
Alexey Khoroshilov <khoroshilov@linuxtesting.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |khoroshilov@linuxtesting.or
| |g
--- Comment #10 from Alexey Khoroshilov <khoroshilov@linuxtesting.org> 2013-02-11 10:04:51 ---
(In reply to comment #4)
> Hmm, I looked at the stack trace again, and I see "sys_inotify_rm_watch" in the
> stack trace. I wonder if this is a generic VFS-level inotify bug, perhaps?
It looks like it is actually a data race in VFS layer:
https://patchwork.kernel.org/patch/1685431/
We observed the same issue with JFS file system.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2013-02-11 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 11:21 [Bug 51391] New: BUG: unable to handle kernel NULL pointer dereference bugzilla-daemon
2012-12-07 16:15 ` [Bug 51391] " bugzilla-daemon
2012-12-07 16:23 ` bugzilla-daemon
2012-12-07 16:25 ` bugzilla-daemon
2012-12-07 17:10 ` bugzilla-daemon
2012-12-07 17:12 ` bugzilla-daemon
2012-12-07 17:39 ` bugzilla-daemon
2012-12-07 18:04 ` bugzilla-daemon
2012-12-07 18:15 ` bugzilla-daemon
2012-12-07 20:13 ` bugzilla-daemon
2012-12-10 8:23 ` bugzilla-daemon
2013-02-11 10:04 ` bugzilla-daemon [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=20130211100451.D64AC11FF22@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.