linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [git pull] mount fixes
@ 2025-06-08 17:24 Al Viro
  2025-06-08 18:53 ` pr-tracker-bot
  0 siblings, 1 reply; 5+ messages in thread
From: Al Viro @ 2025-06-08 17:24 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel

The following changes since commit a82ba839915926f8713183fd023c6d9357bae26c:

  Merge tag 'pull-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2025-05-30 15:04:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes

for you to fetch changes up to 12f147ddd6de7382dad54812e65f3f08d05809fc:

  do_change_type(): refuse to operate on unmounted/not ours mounts (2025-06-07 01:37:56 -0400)

----------------------------------------------------------------
mount-related bugfixes

this cycle regression (well, bugfix for this cycle bugfix for v6.15-rc1 regression)
	do_move_mount(): split the checks in subtree-of-our-ns and entire-anon cases
	selftests/mount_setattr: adapt detached mount propagation test
v6.15	fs: allow clone_private_mount() for a path on real rootfs
v6.11	fs/fhandle.c: fix a race in call of has_locked_children()
v5.15	fix propagation graph breakage by MOVE_MOUNT_SET_GROUP move_mount(2)
v5.15	clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns
v5.7	path_overmount(): avoid false negatives
v3.12	finish_automount(): don't leak MNT_LOCKED from parent to child
v2.6.15	do_change_type(): refuse to operate on unmounted/not ours mounts

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Al Viro (7):
      fs/fhandle.c: fix a race in call of has_locked_children()
      path_overmount(): avoid false negatives
      finish_automount(): don't leak MNT_LOCKED from parent to child
      fix propagation graph breakage by MOVE_MOUNT_SET_GROUP move_mount(2)
      do_move_mount(): split the checks in subtree-of-our-ns and entire-anon cases
      clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns
      do_change_type(): refuse to operate on unmounted/not ours mounts

Christian Brauner (1):
      selftests/mount_setattr: adapt detached mount propagation test

KONDO KAZUMA(近藤 和真) (1):
      fs: allow clone_private_mount() for a path on real rootfs

 fs/namespace.c                                     | 113 +++++++++++++--------
 include/linux/mount.h                              |   3 +-
 .../selftests/mount_setattr/mount_setattr_test.c   |  17 +---
 3 files changed, 74 insertions(+), 59 deletions(-)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [git pull] mount fixes
  2025-06-08 17:24 [git pull] mount fixes Al Viro
@ 2025-06-08 18:53 ` pr-tracker-bot
  0 siblings, 0 replies; 5+ messages in thread
From: pr-tracker-bot @ 2025-06-08 18:53 UTC (permalink / raw)
  To: Al Viro; +Cc: Linus Torvalds, Christian Brauner, linux-fsdevel

The pull request you sent on Sun, 8 Jun 2025 18:24:09 +0100:

> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/35b574a6c2279fe47d13ffafb8389f1adc87a1d1

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [git pull] mount fixes
  2025-08-15 23:33 [PATCHES][RFC][CFT] " Al Viro
@ 2025-08-19 16:12 ` Al Viro
  2025-08-19 17:31   ` Linus Torvalds
  2025-08-19 17:33   ` pr-tracker-bot
  0 siblings, 2 replies; 5+ messages in thread
From: Al Viro @ 2025-08-19 16:12 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Christian Brauner, Jan Kara, Lai, Yi, Tycho Andersen,
	Andrei Vagin, Pavel Tikhomirov, linux-fsdevel

(collected *-by and slightly cleaned the text in commit message of [3/4]; otherwise
identical to what had been posted and sat in #fixes)

The following changes since commit 8742b2d8935f476449ef37e263bc4da3295c7b58:

  Merge tag 'pull-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2025-08-12 12:10:33 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes

for you to fetch changes up to fb924b7b8669503582e003dd7b7340ee49029801:

  change_mnt_propagation(): calculate propagation source only if we'll need it (2025-08-19 12:05:59 -0400)

----------------------------------------------------------------
fixes for several recent mount-related regressions

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

----------------------------------------------------------------
Al Viro (4):
      fix the softlockups in attach_recursive_mnt()
      propagate_umount(): only surviving overmounts should be reparented
      use uniform permission checks for all mount propagation changes
      change_mnt_propagation(): calculate propagation source only if we'll need it

 fs/namespace.c | 41 ++++++++++++++++++++++-------------------
 fs/pnode.c     | 10 ++++++----
 2 files changed, 28 insertions(+), 23 deletions(-)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [git pull] mount fixes
  2025-08-19 16:12 ` [git pull] " Al Viro
@ 2025-08-19 17:31   ` Linus Torvalds
  2025-08-19 17:33   ` pr-tracker-bot
  1 sibling, 0 replies; 5+ messages in thread
From: Linus Torvalds @ 2025-08-19 17:31 UTC (permalink / raw)
  To: Al Viro
  Cc: Christian Brauner, Jan Kara, Lai, Yi, Tycho Andersen,
	Andrei Vagin, Pavel Tikhomirov, linux-fsdevel

On Tue, 19 Aug 2025 at 09:12, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> (collected *-by and slightly cleaned the text in commit message of [3/4]; otherwise
> identical to what had been posted and sat in #fixes)

Minor note relating to my workflow: I almost overlooked this pull
request, because it was a continuation of a thread with the subject
"[PATCHES][RFC][CFT]", and then shows up in my mailbox as part of that
thread.

So even though you had removed those RFC/CFT notes from the subject
line, that ended up being not entirely obvious in my MUA, and I was
about to archive the email before I started looking closer.

Now, this time I obviously caught it, but in general it might be safer
to make it more obvious that it has gone from a RFC to a "this is a
real pull".  Not being threaded is obviously one way, or just a bigger
note to make it more obvious.

And hey, this is not generally a huge problem. I could miss emails for
other random reasons like flaky spam detectors or just plain
(hopefully rare) incompetence on my part.

So obviously the general fix to "why didn't Linus pull" is to send me
a follow-up email reminding me about missed pull requests, but I
thought I'd mention this as a "avoid potential delays and confusion"
thing.

              Linus

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [git pull] mount fixes
  2025-08-19 16:12 ` [git pull] " Al Viro
  2025-08-19 17:31   ` Linus Torvalds
@ 2025-08-19 17:33   ` pr-tracker-bot
  1 sibling, 0 replies; 5+ messages in thread
From: pr-tracker-bot @ 2025-08-19 17:33 UTC (permalink / raw)
  To: Al Viro
  Cc: Linus Torvalds, Christian Brauner, Jan Kara, Lai, Yi,
	Tycho Andersen, Andrei Vagin, Pavel Tikhomirov, linux-fsdevel

The pull request you sent on Tue, 19 Aug 2025 17:12:28 +0100:

> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b19a97d57c15643494ac8bfaaa35e3ee472d41da

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2025-08-19 17:33 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-08 17:24 [git pull] mount fixes Al Viro
2025-06-08 18:53 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2025-08-15 23:33 [PATCHES][RFC][CFT] " Al Viro
2025-08-19 16:12 ` [git pull] " Al Viro
2025-08-19 17:31   ` Linus Torvalds
2025-08-19 17:33   ` pr-tracker-bot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).