[Bug 205569] potential data race (likely benign) on inode->i_state (reading and writing to different bits)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: linux-ext4@xxxxxxxxxxxxxxx
Subject: [Bug 205569] potential data race (likely benign) on inode->i_state (reading and writing to different bits)
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 19 Nov 2019 01:26:21 +0000
In-reply-to: <bug-205569-13602@https.bugzilla.kernel.org/>
References: <bug-205569-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205569

--- Comment #3 from Theodore Tso (tytso@xxxxxxx) ---
Yes, it's benign.   An inode which is I_NEW or I_FREEING will never be in the
writeback.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

References:
- [Bug 205569] New: potential data race (likely benign) on inode->i_state (reading and writing to different bits)
  - From: bugzilla-daemon

Prev by Date: Re: [PATCH v4 linux-kselftest-test 4/6] kunit: remove timeout dependence on sysctl_hung_task_timeout_seconds
Next by Date: [Bug 205569] potential data race (likely benign) on inode->i_state (reading and writing to different bits)
Previous by thread: [Bug 205569] potential data race (likely benign) on inode->i_state (reading and writing to different bits)
Next by thread: [Bug 205569] potential data race (likely benign) on inode->i_state (reading and writing to different bits)
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux