linux-ext4 - Re: [Bug 14734] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000808

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]

Date:	Sat, 5 Dec 2009 22:03:53 -0500
From:	tytso@....edu
To:	bugzilla-daemon@...zilla.kernel.org
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [Bug 14734] New: BUG: unable to handle kernel NULL pointer
 dereference at 0000000000000808

On Fri, Dec 04, 2009 at 03:39:30PM +0000, bugzilla-daemon@...zilla.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
--
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