From: Al Viro <viro@ZenIV.linux.org.uk>
To: Suresh Jayaraman <sjayaraman@suse.de>
Cc: Steve French <smfrench@gmail.com>,
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 05:18:43 +0000 [thread overview]
Message-ID: <20110120051843.GO22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4D37C1AE.7040100@suse.de>
On Thu, Jan 20, 2011 at 10:31:34AM +0530, Suresh Jayaraman wrote:
> 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
It is in the mainline. And there's no way anybody could've seen such
trace on .37 or earlier, since d_set_d_op() didn't exist before that.
prev parent reply other threads:[~2011-01-20 5:18 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
2011-01-20 5:18 ` Al Viro [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=20110120051843.GO22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=htmldeveloper@gmail.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjayaraman@suse.de \
--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