From: Chao Yu <chao@kernel.org>
To: Wu Bo <bo.wu@vivo.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] f2fs do DIO write make file corruption
Date: Wed, 11 Aug 2021 11:03:11 +0800 [thread overview]
Message-ID: <6519b8b7-1eb0-f286-7593-5c5ebbfb5554@kernel.org> (raw)
In-Reply-To: <5b68208b-fd94-bf4e-fc4b-d79d13abf1c6@vivo.com>
On 2021/8/11 10:48, Wu Bo wrote:
> I use the following command to create a file, the file may got corruption:
> f2fs_io write 2 0 512 inc_num dio $path
>
> And when I use bio or to set the chunk size to 1 block, the file is
> normal. The commands as following:
> f2fs_io write 2 0 512 inc_num buffered $path
> f2fs_io write 1 0 512 inc_num dio $path
>
> I find this bug on old kernel version 4.14.117, and not find on version
> 4.19.152. So this bug is fixed. Can anyone can tell me which patch fixed
> this bug?
Not sure,
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=7bae8b6b73e46c307fa355ce086800b7ad6610f8
Thanks,
>
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2021-08-11 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 2:48 [f2fs-dev] f2fs do DIO write make file corruption Wu Bo
2021-08-11 3:03 ` Chao Yu [this message]
2021-08-11 3:28 ` Wu Bo
2021-08-11 12:57 ` Chao Yu
2021-08-12 2:55 ` Wu Bo
2021-08-12 12:17 ` Chao Yu
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=6519b8b7-1eb0-f286-7593-5c5ebbfb5554@kernel.org \
--to=chao@kernel.org \
--cc=bo.wu@vivo.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).