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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 9 Aug 2022 17:43:24 +0900 From: Sergey Senozhatsky <senozhatsky@...omium.org> To: Jiri Slaby <jirislaby@...nel.org> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, minchan@...nel.org, ngupta@...are.org, Sergey Senozhatsky <senozhatsky@...omium.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>, avromanov@...rdevices.ru, ddrokosov@...rdevices.ru Subject: Re: ext2/zram issue [was: Linux 5.19] On (22/08/09 10:12), Jiri Slaby wrote: > > So currently, I blame: > > commit e7be8d1dd983156bbdd22c0319b71119a8fbb697 > > Author: Alexey Romanov <avromanov@...rdevices.ru> > > Date: Thu May 12 20:23:07 2022 -0700 > > > > zram: remove double compression logic > > > > > > /me needs to confirm. > > With that commit reverted, I see no more I/O errors, only oom-killer > messages (which is OK IMO, provided I write 1G of urandom on a machine w/ > 800M of RAM): Hmm... So handle allocation always succeeds in the slow path? (when we try to allocate it second time)
Powered by blists - more mailing lists