linux-ext4 - [Bug 51391] BUG: unable to handle kernel NULL pointer dereference

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20121207171221.D8D3111FB81@bugzilla.kernel.org>
Date:	Fri,  7 Dec 2012 17:12:21 +0000 (UTC)
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 51391] BUG: unable to handle kernel NULL pointer dereference

https://bugzilla.kernel.org/show_bug.cgi?id=51391





--- Comment #4 from Theodore Tso <tytso@....edu>  2012-12-07 17:12:21 ---
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?   I
don't have an easy way of setting up an inotify in my bare-bones KVM
environment.  Can you tell me a bit more about your environment and what you
might be using that might be setting an inotify on something on your 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html