linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Zhiguo Niu <niuzhiguo84@gmail.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to avoid racing in between read and OPU dio write
Date: Wed, 26 Jun 2024 22:52:12 +0800	[thread overview]
Message-ID: <f5f4f84d-1719-4e8c-a2ce-71453884b19e@kernel.org> (raw)
In-Reply-To: <CAHJ8P3+VUozoMVHvMxqDrDRVttRWDJ5a4A2ysJv2_O4ytfq8OA@mail.gmail.com>

On 2024/6/26 10:01, Zhiguo Niu wrote:
> Chao Yu <chao@kernel.org> 于2024年6月25日周二 22:29写道:
>>
>> If lfs mode is on, buffered read may race w/ OPU dio write as below,
>> it may cause buffered read hits unwritten data unexpectly, and for
>> dio read, the race condition exists as well.
>>
>> Thread A                        Thread B
>> - f2fs_file_write_iter
>>   - f2fs_dio_write_iter
>>    - __iomap_dio_rw
>>     - f2fs_iomap_begin
>>      - f2fs_map_blocks
>>       - __allocate_data_block
>>        - allocated blkaddr #x
>>         - iomap_dio_submit_bio
>>                                  - f2fs_file_read_iter
>>                                   - filemap_read
>>                                    - f2fs_read_data_folio
>>                                     - f2fs_mpage_readpages
>>                                      - f2fs_map_blocks
>>                                       : get blkaddr #x
>>                                      - f2fs_submit_read_bio
>>                                  IRQ
>>                                  - f2fs_read_end_io
>>                                   : read IO on blkaddr #x complete
>> IRQ
>> - iomap_dio_bio_end_io
>>   : direct write IO on blkaddr #x complete
>>
>> In LFS mode, if there is inflight dio, let's force read to buffered
>> IO, this policy won't cover all race cases, however it is a tradeoff
>> which avoids abusing lock around IO paths.
>>
>> Fixes: f847c699cff3 ("f2fs: allow out-place-update for direct IO in LFS mode")
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>>   fs/f2fs/file.c | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
>> index 278573974db4..866f1a34e92b 100644
>> --- a/fs/f2fs/file.c
>> +++ b/fs/f2fs/file.c
>> @@ -882,6 +882,10 @@ static bool f2fs_force_buffered_io(struct inode *inode, int rw)
>>                  return true;
>>          if (is_sbi_flag_set(sbi, SBI_CP_DISABLED))
>>                  return true;
>> +       /* In LFS mode, if there is inflight dio, force read to buffered IO */
>> +       if (rw == READ && f2fs_lfs_mode(sbi) &&
>> +                       atomic_read(&inode->i_dio_count))
>> +               return false;
> Hi Chao,
> A little doubt:),force “buffered IO” should return "true"?

Oops, too rush to send the patch...

> another want to confirm is, "thread B" in commit msg just doing buffer
> read, so this modification just cover direct read case?

Oh, the fix is incorrect, will look into it soon.

Thanks,

> thanks!
>>
>>          return false;
>>   }
>> --
>> 2.40.1
>>
>>
>>
>> _______________________________________________
>> Linux-f2fs-devel mailing list
>> Linux-f2fs-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2024-06-26 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 14:25 [f2fs-dev] [PATCH v2] f2fs: fix to avoid racing in between read and OPU dio write Chao Yu
2024-06-26  2:01 ` Zhiguo Niu
2024-06-26 14:52   ` Chao Yu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-10  2:39 Chao Yu
2024-05-14 16:09 ` Jaegeuk Kim
2024-05-15  1:42   ` Chao Yu
2024-05-15  4:42     ` Jaegeuk Kim
2024-05-15  6:38       ` Chao Yu
2024-06-06 10:31         ` Chao Yu
2024-05-15  8:32 ` Wu Bo via Linux-f2fs-devel
2024-06-06 10:25   ` Chao Yu
2024-05-15  8:40 ` Markus Elfring via Linux-f2fs-devel
2024-05-17  8:15 ` kernel test robot

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=f5f4f84d-1719-4e8c-a2ce-71453884b19e@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niuzhiguo84@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).