From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/3 RFC] fs: Hole punch vs page cache filling races
Date: Tue, 6 Apr 2021 12:50:48 -0400 [thread overview]
Message-ID: <YGyRaOgCBP5zdLzz@mit.edu> (raw)
In-Reply-To: <YGyQKEamNgszxE+d@mit.edu>
On Tue, Apr 06, 2021 at 12:45:28PM -0400, Theodore Ts'o wrote:
>
> Hmm, I wonder if it somehow got hit by the vger.kernel.org
> instabilities a while back? As near as I can tell your v2 patches
> never were received by:
>
> http://patchwork.ozlabs.org/project/linux-ext4/
>
> (There are no ext4 patches on patchwork.ozlabs.org on February 8th,
> although I do see patches hitting patchwork on February 7th and 9th.)
I just noticed that the V2 patches were only sent to linux-fsdevel and
not cc'ed to linux-ext4. So that explains why I didn't see it on
patchwork. :-)
- Ted
prev parent reply other threads:[~2021-04-06 16:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 16:06 [PATCH 0/3 RFC] fs: Hole punch vs page cache filling races Jan Kara
2021-01-20 16:06 ` [PATCH 1/3] mm: Do not pass iter into generic_file_buffered_read_get_pages() Jan Kara
2021-01-20 16:18 ` Christoph Hellwig
2021-01-20 16:06 ` [PATCH 2/3] mm: Provide address_space operation for filling pages for read Jan Kara
2021-01-20 16:20 ` Christoph Hellwig
2021-01-20 17:27 ` Jan Kara
2021-01-20 17:28 ` Christoph Hellwig
2021-01-20 17:56 ` Matthew Wilcox
2021-04-02 21:17 ` Kent Overstreet
2021-04-06 12:21 ` Jan Kara
2021-01-20 16:06 ` [PATCH 3/3] ext4: Fix stale data exposure when read races with hole punch Jan Kara
2021-01-21 19:27 ` [PATCH 0/3 RFC] fs: Hole punch vs page cache filling races Matthew Wilcox
2021-01-22 14:32 ` Jan Kara
2021-04-02 19:34 ` Theodore Ts'o
2021-04-06 12:17 ` Jan Kara
2021-04-06 16:45 ` Theodore Ts'o
2021-04-06 16:50 ` Theodore Ts'o [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=YGyRaOgCBP5zdLzz@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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).