[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251119-neuzeit-glotz-f690ff656d19@brauner>
Date: Wed, 19 Nov 2025 11:14:34 +0100
From: Christian Brauner <brauner@...nel.org>
To: Ian Kent <raven@...maw.net>
Cc: Christian Brauner <brauner@...nel.org>,
Al Viro <viro@...IV.linux.org.uk>,
Kernel Mailing List <linux-kernel@...r.kernel.org>,
autofs mailing list <autofs@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 1/1] autofs: dont trigger mount if it cant succeed
On Tue, 18 Nov 2025 10:46:31 +0800, Ian Kent wrote:
> If a mount namespace contains autofs mounts, and they are propagation
> private, and there is no namespace specific automount daemon to handle
> possible automounting then attempted path resolution will loop until
> MAXSYMLINKS is reached before failing causing quite a bit of noise in
> the log.
>
> Add a check for this in autofs ->d_automount() so that the VFS can
> immediately return an error in this case. Since the mount is propagation
> private an EPERM return seems most appropriate.
>
> [...]
Applied to the vfs-6.19.autofs branch of the vfs/vfs.git tree.
Patches in the vfs-6.19.autofs branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.19.autofs
[1/1] autofs: dont trigger mount if it cant succeed
https://git.kernel.org/vfs/vfs/c/922a6f34c175
Powered by blists - more mailing lists