From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dave Chinner <david@fromorbit.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs.git - including i_mutex wrappers
Date: Sat, 23 Jan 2016 23:38:00 +0000 [thread overview]
Message-ID: <20160123233800.GS17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20160123230944.GR17997@ZenIV.linux.org.uk>
On Sat, Jan 23, 2016 at 11:09:44PM +0000, Al Viro wrote:
> On Sun, Jan 24, 2016 at 09:44:35AM +1100, Dave Chinner wrote:
>
> > FWIW, I'm not opposed to making such a locking change - I'm more
> > concerned about the fact I'm finding out about plans for such a
> > fundamental locking change from a pull request on the last day of a
> > merge window....
>
> Look at the commit message (*and* pull request posting) of an earlier vfs.git
> pull request in the beginning of this window. Or into the thread back in
> May when it had been first proposed (and pretty much the same patch had been
> generated and posted by Linus). Changes needed for parallel ->lookup() had
> been discussed; it was a side branch of one of the RCU symlink threads and
> ISTR your own postings in it.
See http://www.spinics.net/lists/kernel/msg2160034.html for the former (Jan 12,
two days into this window) and e.g. https://lkml.org/lkml/2015/5/16/297 for
the latter. And yes, you had been Cc'd on that thread back in May, including
the posting in question - even posted in other branches of that thread, both
before and after...
next prev parent reply other threads:[~2016-01-23 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 14:58 [git pull] vfs.git - including i_mutex wrappers Al Viro
2016-01-23 22:34 ` Dave Chinner
2016-01-23 22:44 ` Dave Chinner
2016-01-23 23:09 ` Al Viro
2016-01-23 23:38 ` Al Viro [this message]
2016-01-24 0:53 ` Dave Chinner
2016-01-24 1:41 ` Al Viro
2016-01-24 7:04 ` Dave Chinner
2016-01-24 7:48 ` Al Viro
2016-01-23 23:48 ` Linus Torvalds
2016-01-24 0:26 ` Dave Chinner
2016-01-24 1:20 ` Al Viro
2016-01-24 7:17 ` Dave Chinner
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=20160123233800.GS17997@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).