[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAC1kPDOLT5SXp6f=4ON1Z0kEvnHiCVq4-chyUvLfV-2LEW=Zmg@mail.gmail.com>
Date: Tue, 16 Dec 2025 10:39:31 +0800
From: Chen Linxuan <me@...ck-desk.cn>
To: Christian Brauner <brauner@...nel.org>
Cc: Jan Kara <jack@...e.cz>, me@...ck-desk.cn,
Alexander Viro <viro@...iv.linux.org.uk>, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] vfs: fix EBUSY on FSCONFIG_CMD_CREATE retry
On Mon, Dec 15, 2025 at 7:55 PM Christian Brauner <brauner@...nel.org> wrote:
> Uh, I'm not sure we should do this. If this only affects cgroup v1 then
> I say we should simply not care at all. It's a deprecated api and anyone
> using it uses something that is inherently broken and a big portion of
> userspace has already migrated. The current or upcoming systemd release
> has dropped all cgroup v1 support.
I am not quite sure if nfs will be affected by this or not.
It looks like vfs_get_tree -> nfs_get_tree -> nfs_try_get_tree ->
nfs_try_get_tree ->
nfs_request_mount -> nfs_mount -> rpc_call_sync -> rpc_run_task ->
rpc_execute ->
__rpc_execute -> rpc_wait_bit_killable might return -ERESTARTSYS.
Powered by blists - more mailing lists