linux-kernel - Re: [PATCH 1/2] zram: use zram_read_from

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: <20241211100810.GE2091455@google.com>
Date: Wed, 11 Dec 2024 19:08:10 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
	Minchan Kim <minchan@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] zram: use zram_read_from_zspool() in writeback

On (24/12/11 17:25), Sergey Senozhatsky wrote:
> We only can read pages from zspool in writeback, zram_read_page()
> is not really right in that context not only because it's a more
> generic function that handles ZRAM_WB pages, but also because it
> requires us to unlock slot between slot flag check and actual page
> read.  Use zram_read_from_zspool() instead and do slot flags check
> and page read under the same slot lock.


Andrew, sorry for the noise, please ignore this mini-series.  Let me
re-send it combined with v2 of `zram: split page type read/write handling`
series [1]

[1] https://lore.kernel.org/linux-kernel/20241210105420.1888790-1-senozhatsky@chromium.org