From: yebin <yebin10@huawei.com>
To: Jan Kara <jack@suse.cz>
Cc: <jack@suse.com>, <tytso@mit.edu>, <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 0/2] Fix race between do_invalidatepage and init_page_buffers
Date: Tue, 25 Aug 2020 10:11:29 +0800 [thread overview]
Message-ID: <5F447351.6060207@huawei.com> (raw)
In-Reply-To: <20200824155143.GH24877@quack2.suse.cz>
Your patch certainly can fix the problem with my testcases, but I don't
think it's
a good way. There are other paths that can call do_invalidatepage , for
instance
block ioctl to discard and zero_range.
On 2020/8/24 23:51, Jan Kara wrote:
> Hello,
>
> On Sat 22-08-20 16:22:16, Ye Bin wrote:
>> Ye Bin (2):
>> ext4: Add comment to BUFFER_FLAGS_DISCARD for search code
>> jbd2: Fix race between do_invalidatepage and init_page_buffers
>>
>> fs/buffer.c | 12 +++++++++++-
>> fs/jbd2/journal.c | 7 +++++++
>> include/linux/buffer_head.h | 2 ++
>> 3 files changed, 20 insertions(+), 1 deletion(-)
> Thanks for the good description of the problem and the analysis. I could
> now easily understand what was really happening on your system. I think the
> problem should be fixed differently through - it is a problem of
> block_write_full_page() that it invalidates buffers while JBD2 is working
> with them. Attached patch should also fix the problem. Can you please test
> whether it fixes your testcase as well? Thanks!
>
> Honza
next prev parent reply other threads:[~2020-08-25 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 8:22 [PATCH 0/2] Fix race between do_invalidatepage and init_page_buffers Ye Bin
2020-08-22 8:22 ` [PATCH 1/2] ext4: Add comment to BUFFER_FLAGS_DISCARD for search code Ye Bin
2020-08-22 8:22 ` [PATCH 2/2] jbd2: Fix race between do_invalidatepage and init_page_buffers Ye Bin
2020-08-24 15:51 ` [PATCH 0/2] " Jan Kara
2020-08-25 2:11 ` yebin [this message]
2020-08-25 8:41 ` Jan Kara
2020-11-20 3:36 ` Theodore Y. Ts'o
2020-11-23 16:54 ` Jan Kara
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=5F447351.6060207@huawei.com \
--to=yebin10@huawei.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.