linux-kernel - Re: kernel BUG at include/linux/dcache.h:303

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] [day] [month] [year] [list]

Message-Id: <200611081814.06652.Martin.Weber@cern.ch>
Date:	Wed, 8 Nov 2006 18:14:06 +0100
From:	Martin Weber <Martin.Weber@...n.ch>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Miklos Szeredi <miklos@...redi.hu>, linux-kernel@...r.kernel.org
Subject: Re: kernel BUG at include/linux/dcache.h:303

Hi,

On Wednesday 08 November 2006 18:07, Christoph Hellwig wrote:
> On Wed, Nov 08, 2006 at 05:35:40PM +0100, Miklos Szeredi wrote:
> > > Whatever propritary module shfs is it's most likely the cause.
> > > Please try again without it.
> >
> > While not propritary, shfs _is_ severely broken.  Try sshfs instead
> > which provides similar functionality:
> >
> >   http://fuse.sourceforge.net/sshfs.html
>
> Agreed to that recommendation.  But then again either shfs is so outdated
> that it doesn't even have a MODULE_LICENSE state or the submitter snipped
> away a module without a proper license from the oops report..

SHFS seems to be outdated. Checking on the web reveals the last release and 
web page update was 2.5 years ago. The source contains a license statement:
shfs/Linux-2.6/inode.c:MODULE_LICENSE("GPL");

I have one tainted module (cisco_ipsec) loaded, which was not in the post 
since I did not know of the importance.

M.

-- 
Martin Weber           Office: +49-241-80-27183
I. Physik. Inst. B        Fax: +49-241-80-22661
RWTH Aachen
D-52056 Aachen           http://home.cern.ch/Martin.Weber
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/