[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whxZ=jgc7up5iNBVMhA0HRX2wAKJMNOGA6Ru9Kqb7_eVw@mail.gmail.com>
Date: Sun, 24 Nov 2024 14:43:58 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Al Viro <viro@...iv.linux.org.uk>, Mateusz Guzik <mjguzik@...il.com>,
"Darrick J. Wong" <djwong@...nel.org>, Hao-ran Zheng <zhenghaoran@...a.edu.cn>, brauner@...nel.org,
jack@...e.cz, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
baijiaju1990@...il.com, 21371365@...a.edu.cn
Subject: Re: [RFC] metadata updates vs. fetches (was Re: [PATCH v4] fs: Fix
data race in inode_set_ctime_to_ts)
On Sun, 24 Nov 2024 at 14:34, Matthew Wilcox <willy@...radead.org> wrote:
>
> Could we just do:
>
> again:
> nsec = READ_ONCE(inode->nsec)
> sec = READ_ONCE(inode->sec)
> if (READ_ONCE(inode->nsec) != nsec)
> goto again;
No. You would need to use the right memory ordering barriers.
And make sure the writes are in the right order.
And even then it wouldn't protect against the race in theory, since
two (separate) time writes could make that nsec check work, even when
the 'sec' read wouldn't necessarily match *either* of the matching
nsec cases.
So it might catch some case of value tearing, and make a "this happens
in once in a blue moon" turn into a "this happens once in five blue
moons" situation instead.
But anybody who really cares about this case would presumably still
care about the "once in five blue moons" case too.
Linus
Powered by blists - more mailing lists