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: <Z1qSTM_Eibvw0bM5@infradead.org> Date: Wed, 11 Dec 2024 23:35:40 -0800 From: Christoph Hellwig <hch@...radead.org> To: Theodore Ts'o <tytso@....edu> Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, Christoph Hellwig <hch@...radead.org>, Jens Axboe <axboe@...nel.dk>, caiqingfu <baicaiaichibaicai@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, linux-ext4@...r.kernel.org, linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [bugzilla:219548] the kernel crashes when storing an EXT4 file system in a ZRAM device On Thu, Dec 12, 2024 at 12:37:39AM -0500, Theodore Ts'o wrote: > More generally, any file system which uses the buffer cache, and > doesn't use jbd2 to control when writeback happens, I think is going > to be at risk with a block device which requires stable writes. The > only way to fix this, really, is to have the buffer cache code copy > the data to a bounce buffer, and then issue the write from the bounce > buffer. Should there be a pr_warn_once when using a file systems using the legacy buffer cache interfaces on a device that requires stable pages?
Powered by blists - more mailing lists