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, 19 Nov 2019 01:02:30 +0000 From: bugzilla-daemon@...zilla.kernel.org To: linux-ext4@...r.kernel.org Subject: [Bug 205569] potential data race (likely benign) on inode->i_state (reading and writing to different bits) https://bugzilla.kernel.org/show_bug.cgi?id=205569 --- Comment #2 from Meng Xu (mengxu.gatech@...il.com) --- (In reply to Theodore Tso from comment #1) > The writeback thread is only applicable for data files. While rmdir() is > only applicable for directories. Also, in both of these function traces, > what you referenced is i_state bits being *read*: > > [WRITE] dirty = inode->i_state & I_DIRTY; > ^^^^^ not correct! > > That being said, there are places in fs/fs-writeback.c where i_state is > modified, and there are code paths where ext4_orphan_add() can be called on > regular data files --- just not the ones you've listed in this bug. > > Can you recheck the call traces and make sure they are correct? Hi Ted, My bad, the [WRITE] location is a few lines down the path, inode->i_state &= ~dirty; Best Regards, Meng -- You are receiving this mail because: You are watching the assignee of the bug.
Powered by blists - more mailing lists