From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
kernel-team@fb.com, jack@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] fs: use READ_ONCE/WRITE_ONCE with the i_size helpers
Date: Tue, 29 Oct 2019 18:22:20 +0100 [thread overview]
Message-ID: <20191029172220.GY3001@twin.jikos.cz> (raw)
In-Reply-To: <20191024120843.4n2eh47okn4c635f@MacBook-Pro-91.local>
On Thu, Oct 24, 2019 at 08:08:44AM -0400, Josef Bacik wrote:
> Al,
>
> Will you pick this up, or do you want me to send it along? Thanks,
So is this patch on the way to 5.4-rc or shall we apply the
btrfs-specific fix? Thanks.
prev parent reply other threads:[~2019-10-29 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 20:20 [PATCH] fs: use READ_ONCE/WRITE_ONCE with the i_size helpers Josef Bacik
2019-10-12 0:34 ` Rik van Riel
2019-10-14 8:51 ` Jan Kara
2019-10-14 12:02 ` David Sterba
2019-10-24 12:08 ` Josef Bacik
2019-10-29 17:22 ` David Sterba [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=20191029172220.GY3001@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).