linux-kernel - Re: [PATCH v2 1/5] zram: always chain bio to the parent in read_from_bdev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2f718a2e-9fbd-831a-a505-cecb32140ab7@samsung.com>
Date:   Tue, 11 Apr 2023 09:34:28 +0200
From:   Pankaj Raghav <p.raghav@...sung.com>
To:     Christoph Hellwig <hch@...radead.org>
CC:     <axboe@...nel.dk>, <minchan@...nel.org>, <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

> 
> It will obviously conflict with this patch, so maybe the best thing is
> to get the other page_endio removals into their respective maintainer
> trees, and then just do the final removal of the unused function after
> -rc1.

Alright, I will drop the last patch that removes the page_endio function, and
send it after rc1. I will make the other changes as suggested by you.