From: Dave Chinner <david@fromorbit.com>
To: Liang Chen <liangchen.linux@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, hch@infradead.org,
jmoyer@redhat.com, jack@suse.cz, lczerner@redhat.com
Subject: Re: [PATCH v2] fs: Fix page cache inconsistency when mixing buffered and AIO DIO for bdev
Date: Sat, 7 May 2022 14:28:29 +1000 [thread overview]
Message-ID: <20220507042829.GN1949718@dread.disaster.area> (raw)
In-Reply-To: <20220507041033.9588-1-lchen@localhost.localdomain>
On Sat, May 07, 2022 at 12:10:33PM +0800, Liang Chen wrote:
> From: Liang Chen <liangchen.linux@gmail.com>
>
> As pointed out in commit 332391a, mixing buffered reads and asynchronous
> direct writes risks ending up with a situation where stale data is left
> in page cache while new data is already written to disk. The same problem
> hits block dev fs too. A similar approach needs to be taken here.
>
> Signed-off-by: Liang Chen <liangchen.linux@gmail.com>
> ---
> V2: declare blkdev_sb_init_dio_done_wq static
> ---
> block/fops.c | 87 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 87 insertions(+)
Rather than copying functionality from the two other generic DIO
paths (which we really want to get down to 1!) into this cut down,
less functional DIO path, shouldn't we be spending the effort to
convert the blkdev device to use one of the other generic DIO paths
that already solves this problem and likely gets a lot more test
coverage?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-05-07 4:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 4:10 [PATCH v2] fs: Fix page cache inconsistency when mixing buffered and AIO DIO for bdev Liang Chen
2022-05-07 4:28 ` Dave Chinner [this message]
2022-05-07 8:51 ` Liang Chen
2022-05-18 13:47 ` Christoph Hellwig
2022-06-08 9:48 ` Liang Chen
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=20220507042829.GN1949718@dread.disaster.area \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=lczerner@redhat.com \
--cc=liangchen.linux@gmail.com \
--cc=linux-fsdevel@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 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.