From: Ian Kent <raven@themaw.net>
To: Suresh Jayaraman <sjayaraman@suse.com>
Cc: Jeff Layton <jlayton@redhat.com>,
Steve French <smfrench@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
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 08:56:06 +0800 [thread overview]
Message-ID: <1336006566.4154.8.camel@perseus.themaw.net> (raw)
In-Reply-To: <20120502135044.6d815e62@tlielax.poochiereds.net>
On Wed, 2012-05-02 at 13:50 -0400, 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
> >
> >
> > Suresh
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> 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).
>
> ...and...
>
> - No "theoretical race condition" issues, unless an explanation of how the
> race can be exploited is also provided.
>
> ...and this seems to clearly violate both of those rules. I'd say we
> just go with putting it in 3.4 for now, and keep it in mind if someone
> comes back later and says that it's needed.
>
I have to agree with Jeff.
I just happened to notice it when trying to work out why DFS automounts
weren't happening.
I eventually found that the kernel in use didn't have the d_invalidate()
patch, then realized the potential problem. It would require fairly
heavy demand to trigger so it isn't urgent, especially since no-one has
actually reported it.
Another reason I should have sent this to Steve, not Linus, sorry for
the noise Linus.
Ian
next prev parent reply other threads:[~2012-05-03 1:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 8:18 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 [this message]
2012-05-03 5:49 ` Suresh Jayaraman
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=1336006566.4154.8.camel@perseus.themaw.net \
--to=raven@themaw.net \
--cc=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjayaraman@suse.com \
--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
all inboxes | Powered by JetHome®