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: <172554793835.1268668.9241893620848455490.b4-ty@mit.edu> Date: Thu, 5 Sep 2024 10:53:46 -0400 From: "Theodore Ts'o" <tytso@....edu> To: adilger.kernel@...ger.ca, jack@...e.com, ebiggers@...nel.org, zhangshida <starzhangzsd@...il.com> Cc: "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, zhangshida@...inos.cn Subject: Re: [PATCH v6 0/4] Fix an error caused by improperly dirtied buffer On Fri, 30 Aug 2024 13:37:35 +0800, zhangshida wrote: > On an old kernel version(4.19, ext3, data=journal, pagesize=64k), > an assertion failure will occasionally be triggered by the line below: > --------- > jbd2_journal_commit_transaction > { > ... > J_ASSERT_BH(bh, !buffer_dirty(bh)); > /* > * The buffer on BJ_Forget list and not jbddirty means > ... > } > --------- > > [...] Applied, thanks! [1/4] ext4: persist the new uptodate buffers in ext4_journalled_zero_new_buffers commit: 3910b513fcdf33030798755c722174ef4a827d2a [2/4] ext4: hoist ext4_block_write_begin and replace the __block_write_begin commit: 6b730a405037501a260d6efd24782d2737e65d07 [3/4] ext4: fix a potential assertion failure due to improperly dirtied buffer commit: cb3de5fc876ee9ef2b830c9e6cdafac5c90903ef [4/4] ext4: remove the special buffer dirty handling in do_journal_get_write_access commit: 183aa1d3baea18b199505455a0247b13de826e2f Best regards, -- Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists