From: Suresh Jayaraman <sjayaraman@suse.de>
To: Steve French <smfrench@gmail.com>
Cc: Peter Teoh <htmldeveloper@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-cifs@vger.kernel.org, Jeff Layton <jlayton@redhat.com>
Subject: Re: CIFS related seg fault (v2.6.37)
Date: Thu, 20 Jan 2011 10:31:34 +0530 [thread overview]
Message-ID: <4D37C1AE.7040100@suse.de> (raw)
In-Reply-To: <AANLkTin7jRk6S2XWcRineCtazQb3rgYsBPakV513Ph9n@mail.gmail.com>
On 01/20/2011 10:25 AM, Steve French wrote:
> On Wed, Jan 19, 2011 at 10:45 PM, Suresh Jayaraman <sjayaraman@suse.de> wrote:
>> (Cc linux-cifs@vger.kernel.org)
>>
>> On 01/20/2011 07:05 AM, Peter Teoh wrote:
>>> Filed a bug today:
>>>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=27082
>>>
>>> Version of kernel (linus git tree synced): v2.6.37-3737-g0c21e3a
>>>
>>> Output of dmesg summarized here:
>>>
>>> [ 7273.369563] ------------[ cut here ]------------
>>> [ 7273.369575] kernel BUG at fs/dcache.c:1358!
>>
>> Looks like the issue is already fixed in VFS (see discussion):
>> http://thread.gmane.org/gmane.linux.kernel.cifs/2284
>>
>> Jeff: Looks like the issue is reproducible with 2.6.37 too.. Any idea
>> which is the commit that fixes this problem and whether it has been
>> marked for -stable?
>
> So Jeff's change referenced (to fs/cifs/dir.c) above is not needed due
> to a vfs change?
>
Sorry it was not a VFS fix but a fix from Al Viro that fixed this
problem. IIUC, the commit has made it to cifs-2.6.git but not upstream.
commit 1c929cfe6d8f2087a337a868fbf6c38d56bb4889
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Sat Dec 18 11:43:51 2010 -0500
switch cifs
--
Suresh Jayaraman
next prev parent reply other threads:[~2011-01-20 5:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 1:35 CIFS related seg fault (v2.6.37) Peter Teoh
2011-01-20 4:45 ` Suresh Jayaraman
2011-01-20 4:55 ` Steve French
2011-01-20 4:56 ` Suresh Jayaraman
2011-01-20 5:01 ` Suresh Jayaraman [this message]
2011-01-20 5:18 ` Al Viro
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=4D37C1AE.7040100@suse.de \
--to=sjayaraman@suse.de \
--cc=htmldeveloper@gmail.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.com \
/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