From: NeilBrown <neilb@suse.com>
To: "J. Bruce Fields" <bfields@fieldses.org>,
William Dauchy <wdauchy@gmail.com>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] sunrpc/cache: drop reference when sunrpc_cache_pipe_upcall() detects a race
Date: Wed, 16 Mar 2016 07:37:13 +1100 [thread overview]
Message-ID: <87vb4nh406.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20160315131959.GA419@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
On Wed, Mar 16 2016, J. Bruce Fields wrote:
> On Tue, Mar 15, 2016 at 01:43:37PM +0100, William Dauchy wrote:
>> Hello,
>>
>> On Mon, Mar 14, 2016 at 9:38 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
>> > Sorry for the delay. I agree, it seems simple enough; applying for
>> > 4.6....
>>
>> It it something we can consider for stable?
>
> It's an unlikely-looking race, I haven't seen it reported in the wild,
> and the consequences are just a reference-count leak (though admittedly
> those can sometimes cause crashes later--I haven't checked for that
> here).
>
> So I wasn't planning too, but any additional information's welcomed.
I agree that it isn't needed for stable - the race is tiny and the
consequence of losing the race is that entries get stuck in the cache
and possible an exported filesystem cannot be unmounted. I don't think
that is a problem severe enough to meet the rules for -stable - though I
know the rules aren't always closely followed.
I wouldn't exactly object to it going to stable if someone wanted to
push, but I would rather it didn't appear in -stable before appearing in
a released (not -rc) kernel from Linus.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-03-15 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 6:20 [PATCH] sunrpc/cache: drop reference when sunrpc_cache_pipe_upcall() detects a race NeilBrown
2016-03-14 20:38 ` J. Bruce Fields
2016-03-15 12:43 ` William Dauchy
2016-03-15 13:19 ` J. Bruce Fields
2016-03-15 20:37 ` NeilBrown [this message]
2016-03-16 7:31 ` William Dauchy
2016-03-16 15:05 ` J. Bruce Fields
2016-03-16 15:38 ` William Dauchy
2016-03-16 16:00 ` J. Bruce Fields
2016-03-16 16:16 ` William Dauchy
2016-03-18 6:05 ` NeilBrown
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=87vb4nh406.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=wdauchy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.