From: Suresh Jayaraman <sjayaraman@suse.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Steve French <smfrench@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ian Kent <raven@themaw.net>,
linux-cifs@vger.kernel.org,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cifs - check S_AUTOMOUNT in revalidate
Date: Thu, 03 May 2012 11:19:26 +0530 [thread overview]
Message-ID: <4FA21C66.1030009@suse.com> (raw)
In-Reply-To: <20120502135044.6d815e62@tlielax.poochiereds.net>
On 05/02/2012 11:20 PM, Jeff Layton wrote:
> On Wed, 02 May 2012 17:15:29 +0530
> Suresh Jayaraman <sjayaraman@suse.com> wrote:
>
>> On 04/28/2012 09:03 AM, Steve French wrote:
>>> The fix makes sense, but it is fairly recent and I haven't had a
>>> chance to try it,
>>> so unless a new release is imminent, I would prefer to put in the next merge
>>> request (I have at least one more fix likely as well) next week.
>>
>> We need this fix for -stable as well, right? Please include
>>
>> Cc: stable@vger.kernel.org
>
> The stable-kernel-rules.txt file says this:
>
> - It must fix a real bug that bothers people (not a, "This could be a
> problem..." type thing).
>
Doh, looks like I had assumed (wrongly) that this fixes the problem
reported here
http://marc.info/?l=linux-cifs&m=133460168320472&w=2
(mapping to a dfsroot and cd to a reflink returning "Object is remote"
or "Not a directory" error). I didn't have a setup to verify it too.
I notice that Steve has already merged this patch adding Cc to stable
and the Cc has to be removed before sending the pull request.
Suresh
prev parent reply other threads:[~2012-05-03 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 8:18 [PATCH] cifs - check S_AUTOMOUNT in revalidate Ian Kent
2012-04-28 2:46 ` Linus Torvalds
2012-04-28 3:33 ` Steve French
2012-04-28 3:55 ` Linus Torvalds
2012-05-02 11:45 ` Suresh Jayaraman
2012-05-02 17:50 ` Jeff Layton
2012-05-03 0:56 ` Ian Kent
2012-05-03 5:49 ` Suresh Jayaraman [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=4FA21C66.1030009@suse.com \
--to=sjayaraman@suse.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=smfrench@gmail.com \
--cc=torvalds@linux-foundation.org \
/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