[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZFp6GphV3H0eyrH+@redhat.com>
Date: Tue, 9 May 2023 12:51:38 -0400
From: Mike Snitzer <snitzer@...nel.org>
To: Sarthak Kukreti <sarthakkukreti@...omium.org>
Cc: dm-devel@...hat.com, linux-block@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
Theodore Ts'o <tytso@....edu>,
"Michael S. Tsirkin" <mst@...hat.com>,
"Darrick J. Wong" <djwong@...nel.org>,
Jason Wang <jasowang@...hat.com>,
Bart Van Assche <bvanassche@...gle.com>,
stable@...r.kernel.org, Christoph Hellwig <hch@...radead.org>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Stefan Hajnoczi <stefanha@...hat.com>,
Brian Foster <bfoster@...hat.com>,
Alasdair Kergon <agk@...hat.com>
Subject: Re: [PATCH v6 1/5] block: Don't invalidate pagecache for invalid
falloc modes
On Sat, May 06 2023 at 2:29P -0400,
Sarthak Kukreti <sarthakkukreti@...omium.org> wrote:
> Only call truncate_bdev_range() if the fallocate mode is
> supported. This fixes a bug where data in the pagecache
> could be invalidated if the fallocate() was called on the
> block device with an invalid mode.
>
> Fixes: 25f4c41415e5 ("block: implement (some of) fallocate for block devices")
> Cc: stable@...r.kernel.org
> Reported-by: Darrick J. Wong <djwong@...nel.org>
> Signed-off-by: Sarthak Kukreti <sarthakkukreti@...omium.org>
Reviewed-by: Mike Snitzer <snitzer@...nel.org>
Powered by blists - more mailing lists