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
| ||
|
Message-ID: <YvJhIU/6ysqLyxrj@google.com> Date: Tue, 9 Aug 2022 22:29:05 +0900 From: Sergey Senozhatsky <senozhatsky@...omium.org> To: Aleksey Romanov <AVRomanov@...rdevices.ru> Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, Dmitry Rokosov <DDRokosov@...rdevices.ru>, Jiri Slaby <jirislaby@...nel.org>, Minchan Kim <minchan@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "ngupta@...are.org" <ngupta@...are.org>, Jan Kara <jack@...e.com>, Ted Ts'o <tytso@....edu>, Andreas Dilger <adilger.kernel@...ger.ca>, Ext4 Developers List <linux-ext4@...r.kernel.org> Subject: Re: ext2/zram issue [was: Linux 5.19] On (22/08/09 13:15), Aleksey Romanov wrote: > On Tue, Aug 09, 2022 at 08:53:36PM +0900, Sergey Senozhatsky wrote: > > > If you make the decision to revert slow path removal patch, I would > > > prefer to review the original patch with unneeded code removal again > > > if you don't mind: > > > https://lore.kernel.org/linux-block/20220422115959.3313-1-avromanov@sberdevices.ru/ > > > > Sure, we can return to it after the merge window. > > In that case, do I need to send my original patch again? Would be nice, since the patch needs rebasing (due to zsmalloc PTR_ERR changes)
Powered by blists - more mailing lists