From: Alexander Monakov <amonakov@ispras.ru>
To: linux-fsdevel@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: ETXTBSY window in __fput
Date: Fri, 29 Aug 2025 10:21:35 +0300 (MSK) [thread overview]
Message-ID: <5a4513fe-6eae-9269-c235-c8b0bc1ae05b@ispras.ru> (raw)
In-Reply-To: <6e60aa72-94ef-9de2-a54c-ffd91fcc4711@ispras.ru>
On Wed, 27 Aug 2025, Alexander Monakov wrote:
> Dear fs hackers,
>
> I suspect there's an unfortunate race window in __fput where file locks are
> dropped (locks_remove_file) prior to decreasing writer refcount
> (put_file_access). If I'm not mistaken, this window is observable and it
> breaks a solution to ETXTBSY problem on exec'ing a just-written file, explained
> in more detail below.
The race in __fput is a problem irrespective of how the testcase triggers it,
right? It's just showing a real-world scenario. But the issue can be
demonstrated without a multithreaded fork: imagine one process placing an
exclusive lock on a file and writing to it, another process waiting on that
lock and immediately execve'ing when the lock is released.
Can put_file_access be moved prior to locks_remove_file in __fput?
Alexander
next prev parent reply other threads:[~2025-08-29 7:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 21:05 Alexander Monakov
2025-08-26 22:00 ` Al Viro
2025-08-27 7:22 ` Alexander Monakov
2025-08-27 11:52 ` Theodore Ts'o
2025-08-27 13:05 ` Alexander Monakov
2025-08-31 19:22 ` David Laight
2025-09-01 8:44 ` Jan Kara
2025-08-27 13:16 ` Aleksa Sarai
2025-08-27 14:29 ` Alexander Monakov
2025-08-29 7:21 ` Alexander Monakov [this message]
2025-08-29 9:47 ` Christian Brauner
2025-08-29 10:17 ` Alexander Monakov
2025-08-29 11:07 ` Christian Brauner
2025-08-29 11:45 ` Alexander Monakov
2025-08-29 14:02 ` Jan Kara
2025-09-01 17:53 ` Alexander Monakov
2025-09-02 10:36 ` Jan Kara
2025-08-29 18:32 ` Colin Walters
2025-09-01 18:39 ` Mateusz Guzik
2025-09-01 19:57 ` Colin Walters
2025-09-01 20:22 ` Mateusz Guzik
2025-09-02 8:33 ` Christian Brauner
2025-09-02 8:44 ` Mateusz Guzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a4513fe-6eae-9269-c235-c8b0bc1ae05b@ispras.ru \
--to=amonakov@ispras.ru \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®