From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 14734] BUG: unable to handle kernel NULL pointer dereference at 0000000000000808
Date: Sun, 6 Dec 2009 21:02:18 GMT [thread overview]
Message-ID: <200912062102.nB6L2IEc004168@demeter.kernel.org> (raw)
In-Reply-To: <bug-14734-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14734
--- Comment #1 from Theodore Tso <tytso@mit.edu> 2009-12-06 21:02:16 ---
On Fri, Dec 04, 2009 at 03:39:30PM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
>
> Just let me know what else I should post in addition to the following. I've
> gotten this bug pretty consistently, on 2.6.
Hmm.... there's a strnage fsnotify_clear_marks_by_inode() on the stack
trace which doesn't seem to make any sense and which I can't place.
Are you using the fsnotify feature for some reason (i.e., some
new-fangled proprietnary "linux anti-virus" package or some such?).
If so, does the problem go away if you stop using said package and not
use the fsnotify interface?
Also, do you have to do anything special to trigger it? Is the "rm"
in the process handle an "rm -rf", or some such?
- Ted
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-12-06 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 15:39 [Bug 14734] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000808 bugzilla-daemon
2009-12-06 3:03 ` tytso
2009-12-06 21:02 ` bugzilla-daemon [this message]
2009-12-09 12:27 ` [Bug 14734] " bugzilla-daemon
2009-12-09 13:45 ` bugzilla-daemon
[not found] <bug-14734-13602@https.bugzilla.kernel.org/>
2012-06-18 13:01 ` bugzilla-daemon
2012-06-18 13:01 ` bugzilla-daemon
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=200912062102.nB6L2IEc004168@demeter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).