From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
"frank.li@vivo.com" <frank.li@vivo.com>,
"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"brauner@kernel.org" <brauner@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file()
Date: Thu, 10 Jul 2025 07:03:18 +0900 [thread overview]
Message-ID: <3efa3d2a-e98f-43ee-91dd-5aeefcff75e1@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <316f8d5b06aed08bd979452c932cbce2341a8a56.camel@ibm.com>
On 2025/07/10 3:33, Viacheslav Dubeyko wrote:
> My worry that we could have a race condition here. Let's imagine that two
> threads are trying to call __hfsplus_setxattr() and both will try to create the
> Attributes File. Potentially, we could end in situation when inode could have
> not zero size during hfsplus_create_attributes_file() in one thread because
> another thread in the middle of Attributes File creation. Could we double check
> that we don't have the race condition here? Otherwise, we need to make much
> cleaner fix of this issue.
I think that there is some sort of race window, for
https://elixir.bootlin.com/linux/v6.15.5/source/fs/hfsplus/xattr.c#L145
explains that if more than one thread concurrently reached
if (!HFSPLUS_SB(inode->i_sb)->attr_tree) {
err = hfsplus_create_attributes_file(inode->i_sb);
if (unlikely(err))
goto end_setxattr;
}
path, all threads except one thread will fail with -EAGAIN.
next prev parent reply other threads:[~2025-07-09 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 10:10 Tetsuo Handa
2025-06-30 17:18 ` Viacheslav Dubeyko
2025-07-07 14:22 ` Yangtao Li
2025-07-07 14:45 ` Tetsuo Handa
2025-07-07 19:03 ` Viacheslav Dubeyko
2025-07-09 14:02 ` Tetsuo Handa
2025-07-09 18:33 ` Viacheslav Dubeyko
2025-07-09 22:03 ` Tetsuo Handa [this message]
2025-07-11 11:35 ` Tetsuo Handa
2025-07-11 17:21 ` Viacheslav Dubeyko
2025-07-12 11:22 ` Tetsuo Handa
2025-07-14 23:30 ` Viacheslav Dubeyko
2025-07-15 5:17 ` [PATCH v2] " Tetsuo Handa
2025-07-15 18:49 ` Viacheslav Dubeyko
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=3efa3d2a-e98f-43ee-91dd-5aeefcff75e1@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=Slava.Dubeyko@ibm.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
/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®