From: Jeff Layton <jlayton@poochiereds.net>
To: William Dauchy <wdauchy@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Bruce Fields <bfields@fieldses.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Kostya Serebryany <kcc@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Alexander Potapenko <glider@google.com>,
ktsan <ktsan@googlegroups.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] fs: fix data races on inode->i_flctx
Date: Mon, 19 Oct 2015 13:46:06 -0400 [thread overview]
Message-ID: <1445276766.10328.0.camel@poochiereds.net> (raw)
In-Reply-To: <CAJ75kXZ9N5vnDHXTpoY2ZpzO9o=Crq8wo3w-Ngf=Wj9Ew87z8w@mail.gmail.com>
On Mon, 2015-10-19 at 19:24 +0200, William Dauchy wrote:
> On Mon, Oct 19, 2015 at 6:53 PM, William Dauchy <wdauchy@gmail.com>
> wrote:
> > On Mon, Oct 19, 2015 at 6:44 PM, Jeff Layton <
> > jlayton@poochiereds.net> wrote:
> > > This should be fixed by this series of four commits that are
> > > already in
> > > mainline:
> > > bcd7f78d078ff6197715c1ed070c92aca57ec12c..ee296d7c5709440f8abd36b
> > > 5b65c6
> > > b3e388538d9
> >
> > Am I missing something, I see three of them between
> > bcd7f78d078ff6197715c1ed070c92aca57ec12c..ee296d7c5709440f8abd36b5b
> > 65c6b3e388538d9
> > (and not four)
> >
> > ee296d7c5709440f8abd36b5b65c6b3e388538d9 locks: inline
> > posix_lock_file_wait and flock_lock_file_wait
> > 83bfff23e9ed19f37c4ef0bba84e75bd88e5cf21 nfs4: have do_vfs_lock
> > take
> > an inode pointer
> > 29d01b22eaa18d8b46091d3c98c6001c49f78e4a locks: new helpers -
> > flock_lock_inode_wait and posix_lock_inode_wait
>
> I suppose I found the missing one
> bcd7f78 locks: have flock_lock_file take an inode pointer instead of
> a filp
>
Ahh yes, sorry -- that one is also required.
Thanks!
--
Jeff Layton <jlayton@poochiereds.net>
prev parent reply other threads:[~2015-10-19 17:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 7:43 [PATCH] fs: fix data races on inode->i_flctx Dmitry Vyukov
2015-09-21 10:50 ` Jeff Layton
2015-09-21 10:53 ` Dmitry Vyukov
2015-09-21 10:56 ` Jeff Layton
2015-09-21 11:00 ` Dmitry Vyukov
2015-09-21 11:17 ` Jeff Layton
2015-09-21 11:38 ` Dmitry Vyukov
2015-09-21 11:44 ` Jeff Layton
2015-09-21 11:53 ` Dmitry Vyukov
2015-10-19 15:18 ` William Dauchy
2015-10-19 15:27 ` Dmitry Vyukov
2015-10-19 15:36 ` William Dauchy
2015-10-19 16:44 ` Jeff Layton
2015-10-19 16:53 ` William Dauchy
2015-10-19 17:24 ` William Dauchy
2015-10-19 17:46 ` Jeff Layton [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=1445276766.10328.0.camel@poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=andreyknvl@google.com \
--cc=bfields@fieldses.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=ktsan@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).