linux-kernel - Re: [PATCH v5 2/5] Revert "frontswap: simplify frontswap_register

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Wed, 21 Sep 2022 09:42:41 +0800
From:   Liu Shixin <liushixin2@...wei.com>
To:     Christoph Hellwig <hch@....de>
CC:     Seth Jennings <sjenning@...hat.com>,
        Dan Streetman <ddstreet@...e.org>,
        Vitaly Wool <vitaly.wool@...sulko.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Nathan Chancellor <nathan@...nel.org>, <linux-mm@...ck.org>,
        <linux-kernel@...r.kernel.org>,
        Kefeng Wang <wangkefeng.wang@...wei.com>
Subject: Re: [PATCH v5 2/5] Revert "frontswap: simplify
 frontswap_register_ops"

On 2022/9/20 20:13, Christoph Hellwig wrote:

> On Thu, Sep 15, 2022 at 11:50:00AM +0800, Liu Shixin wrote:
>> This reverts commit f328c1d16e4c764992895ac9c9425cea861b2ca0.
>>
>> Since we are supported to delay zswap initializaton, we need to invoke
>> ops->init for the swap device which is already online when register
>> backend.
> Why do we "have" to do it.  Retroactively supporting functionality on
> previously enabled swap devices seems rather odd, and the amount of
> cruft added for it here absolutely does not seem to be worth it.
Hi Christoph,

This revert makes code complicated, but I think it's necessary. When enable zswap,
I expect it to work for all swap devices as much as possible. In this way, user can enable
zswap and swap device in any order. Since we can enable zswap on previously swap
devices, why not support it to get such benifit?

Thanks,
> .
>