From: William Dauchy <william@gandi.net>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: William Dauchy <william@gandi.net>,
Linux NFS mailing list <linux-nfs@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
jloup@gandi.net
Subject: Re: extra reference to fl->fl_file, possible regression
Date: Fri, 10 Jul 2015 17:06:59 +0200 [thread overview]
Message-ID: <20150710150659.GP15144@gandi.net> (raw)
In-Reply-To: <20150710103914.78189580@tlielax.poochiereds.net>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
On Jul10 10:39, Jeff Layton wrote:
> So if a file happened to have some flock locks on it, then we could
> be taking a new reference to a file that has already had its refcount
> go to zero.
do you have any test case which may confirm that?
in the commit messages, you also were refering to some tests; I wonder
if you could share it.
--
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-07-10 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 9:29 extra reference to fl->fl_file, possible regression William Dauchy
2015-07-10 11:24 ` Jeff Layton
2015-07-10 11:36 ` William Dauchy
2015-07-10 12:54 ` William Dauchy
2015-07-10 14:39 ` Jeff Layton
2015-07-10 15:06 ` William Dauchy [this message]
2015-07-10 15:18 ` Jeff Layton
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=20150710150659.GP15144@gandi.net \
--to=william@gandi.net \
--cc=jlayton@poochiereds.net \
--cc=jloup@gandi.net \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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