Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 4 Apr 2023 23:07:04 -0700
From:   Christoph Hellwig <hch@infradead.org>
To:     Andrew Morton <akpm@linux-foundation.org>
Cc:     Christoph Hellwig <hch@infradead.org>,
        Pankaj Raghav <p.raghav@samsung.com>, axboe@kernel.dk,
        minchan@kernel.org, martin@omnibond.com, hubcap@omnibond.com,
        brauner@kernel.org, viro@zeniv.linux.org.uk,
        senozhatsky@chromium.org, willy@infradead.org, hch@lst.de,
        devel@lists.orangefs.org, mcgrof@kernel.org,
        linux-block@vger.kernel.org, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, gost.dev@samsung.com,
        linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] zram: always chain bio to the parent in
 read_from_bdev_async
Message-ID: <ZC0QCJM6Rl39jnGU@infradead.org>
References: <20230403132221.94921-1-p.raghav@samsung.com>
 <CGME20230403132223eucas1p2a27e8239b8bda4fc16b675a9473fd61f@eucas1p2.samsung.com>
 <20230403132221.94921-2-p.raghav@samsung.com>
 <ZCw9Dxdd0C95EUza@infradead.org>
 <20230404123131.6e8fca22b0a484c8c152492a@linux-foundation.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230404123131.6e8fca22b0a484c8c152492a@linux-foundation.org>
Precedence: bulk

On Tue, Apr 04, 2023 at 12:31:31PM -0700, Andrew Morton wrote:
> >  I've now sent a series to untangle
> > and fix up the zram I/O path, which should address the underlying
> > issue here.
> 
> I can't find that series.

https://lore.kernel.org/linux-block/20230404150536.2142108-1-hch@lst.de/T/#t