[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZCtC4yhM5lZP7mEg@google.com>
Date: Mon, 3 Apr 2023 14:19:31 -0700
From: Minchan Kim <minchan@...nel.org>
To: Pankaj Raghav <p.raghav@...sung.com>
Cc: axboe@...nel.dk, martin@...ibond.com, hubcap@...ibond.com,
brauner@...nel.org, viro@...iv.linux.org.uk,
senozhatsky@...omium.org, akpm@...ux-foundation.org,
willy@...radead.org, hch@....de, devel@...ts.orangefs.org,
mcgrof@...nel.org, linux-block@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, gost.dev@...sung.com,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] zram: always chain bio to the parent in
read_from_bdev_async
On Mon, Apr 03, 2023 at 03:22:17PM +0200, Pankaj Raghav wrote:
> zram_bvec_read() is called with the bio set to NULL only in
> writeback_store() function. When a writeback is triggered,
> zram_bvec_read() is called only if ZRAM_WB flag is not set. That will
> result only calling zram_read_from_zspool() in __zram_bvec_read().
>
> rw_page callback used to call read_from_bdev_async with a NULL parent
> bio but that has been removed since commit 3222d8c2a7f8
> ("block: remove ->rw_page").
>
> We can now safely always call bio_chain() as read_from_bdev_async() will
> be called with a parent bio set. A WARN_ON_ONCE is added if this function
> is called with parent set to NULL.
>
> Signed-off-by: Pankaj Raghav <p.raghav@...sung.com>
Acked-by: Minchan Kim <minchan@...nel.org>
Thanks.
Powered by blists - more mailing lists