diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-12-01 16:38:21 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-12-01 16:38:21 -0800 |
| commit | ffbf700df204dd25a48a19979a126e37f5dd1e6a (patch) | |
| tree | d92bf07cda161c226d90baef25423faa65a8acbf /fs/namespace.c | |
| parent | d0deeb803cd65c41c37ac106063c46c51d5d43ab (diff) | |
| parent | 922a6f34c1756d2b0c35d9b2d915b8af19e85965 (diff) | |
| download | random-ffbf700df204dd25a48a19979a126e37f5dd1e6a.tar.gz | |
Merge tag 'vfs-6.19-rc1.autofs' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs
Pull autofs update from Christian Brauner:
"Prevent futile mount triggers in private mount namespaces.
Fix a problematic loop in autofs when a mount namespace contains
autofs mounts that are propagation private and there is no
namespace-specific automount daemon to handle possible automounting.
Previously, attempted path resolution would loop until MAXSYMLINKS was
reached before failing, causing significant noise in the log.
The fix adds a check in autofs ->d_automount() so that the VFS can
immediately return EPERM in this case. Since the mount is propagation
private, EPERM is the most appropriate error code"
* tag 'vfs-6.19-rc1.autofs' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs:
autofs: dont trigger mount if it cant succeed
Diffstat (limited to 'fs/namespace.c')
| -rw-r--r-- | fs/namespace.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/fs/namespace.c b/fs/namespace.c index d7afac807ac38b..35960fd00ee094 100644 --- a/fs/namespace.c +++ b/fs/namespace.c @@ -5148,6 +5148,12 @@ static u64 mnt_to_propagation_flags(struct mount *m) return propagation; } +u64 vfsmount_to_propagation_flags(struct vfsmount *mnt) +{ + return mnt_to_propagation_flags(real_mount(mnt)); +} +EXPORT_SYMBOL_GPL(vfsmount_to_propagation_flags); + static void statmount_sb_basic(struct kstatmount *s) { struct super_block *sb = s->mnt->mnt_sb; |