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: <164823418309.637667.12757298463000030100.b4-ty@mit.edu> Date: Fri, 25 Mar 2022 14:49:50 -0400 From: "Theodore Ts'o" <tytso@....edu> To: linux-ext4@...r.kernel.org, Artem Blagodarenko <artem.blagodarenko@...il.com> Cc: "Theodore Ts'o" <tytso@....edu>, adilger.kernel@...ger.ca, Andrew Perepechko <andrew.perepechko@....com> Subject: Re: [PATCH v2] ext4: truncate during setxattr leads to kernel panic On Sat, 12 Mar 2022 18:18:30 -0500, Artem Blagodarenko wrote: > From: Andrew Perepechko <andrew.perepechko@....com> > > When changing a large xattr value to a different large xattr value, > the old xattr inode is freed. Truncate during the final iput causes > current transaction restart. Eventually, parent inode bh is marked > dirty and kernel panic happens when jbd2 figures out that this bh > belongs to the committed transaction. > > [...] Applied, thanks! [1/1] ext4: truncate during setxattr leads to kernel panic commit: c7cded845fc192cc35a1ca37c0cd957ee35abdf8 Best regards, -- Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists