mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Weber <Martin.Weber@cern.ch>
To: Christoph Hellwig <hch@infradead.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at include/linux/dcache.h:303
Date: Wed, 8 Nov 2006 18:14:06 +0100	[thread overview]
Message-ID: <200611081814.06652.Martin.Weber@cern.ch> (raw)
In-Reply-To: <20061108170709.GA30221@infradead.org>

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

      reply	other threads:[~2006-11-08 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 16:08 Martin Weber
2006-11-08 16:12 ` Christoph Hellwig
2006-11-08 16:35   ` Miklos Szeredi
2006-11-08 17:07     ` Christoph Hellwig
2006-11-08 17:14       ` Martin Weber [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=200611081814.06652.Martin.Weber@cern.ch \
    --to=martin.weber@cern.ch \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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

all inboxes | Powered by JetHome®