All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Christian Brauner" <brauner@kernel.org>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH 09/17] selftests/filesystems: check that a mount namespace file on top doesn't bury a mount
Date: Wed, 30 Sep 2026 13:40:00 +0000	[thread overview]
Message-ID: <20260930134000.9030C1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260930-work-mount-fixes-3-v1-9-be34c83956ae@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] selftests: test hangs if child unshare() fails due to unclosed pipe
--

commit b1881c835955f20f1fe11ad422bd61758e3f6d5b
Author: Christian Brauner <brauner@kernel.org>

selftests/filesystems: check that a mount namespace file on top doesn't bury a mount

This commit adds a test for moving a mount with a mount namespace file on
top of it. It ensures that when a mount is moved onto a shared mount, its
copy propagates correctly to slaves without being buried.

> diff --git a/tools/testing/selftests/filesystems/mount_cycle/overmount_ns_file_test.c b/tools/testing/selftests/filesystems/mount_cycle/overmount_ns_file_test.c
> new file mode 100644
> index 0000000000000..c24436a17c0fd
> --- /dev/null
> +++ b/tools/testing/selftests/filesystems/mount_cycle/overmount_ns_file_test.c
> @@ -0,0 +1,187 @@

[ ... ]

> +TEST_F(overmount_ns_file, existing_mount_stays_on_top)
> +{

[ ... ]

> +	/* a newer mount namespace whose file can be bound */
> +	ASSERT_EQ(pipe(pfd), 0);
> +	self->child = fork();
> +	ASSERT_GE(self->child, 0);
> +	if (self->child == 0) {
> +		if (unshare(CLONE_NEWNS) || write(pfd[1], "r", 1) != 1)
> +			_exit(1);
> +		pause();
> +		_exit(0);
> +	}
> +	ASSERT_EQ(read(pfd[0], &c, 1), 1);

[Severity: Medium]
Will this test hang if unshare(CLONE_NEWNS) fails in the child process?

If the child process exits via _exit(1) due to unshare() failing, it closes
its file descriptors. But since the parent process never closed its own copy
of the pipe's write end (pfd[1]), the pipe is not considered closed.

The read() call here will block forever waiting for data instead of returning
an EOF, causing the test program to hang indefinitely.

Should the parent close(pfd[1]) before attempting to read from pfd[0]?

> +	snprintf(s, sizeof(s), "/proc/%d/ns/mnt", self->child);
> +	ASSERT_EQ(mount(s, p, NULL, MS_BIND, NULL), 0);
> +
> +	ASSERT_STREQ(read_file(b, buf, sizeof(buf)), "Q");

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260930-work-mount-fixes-3-v1-0-be34c83956ae@kernel.org?part=9

  reply	other threads:[~2026-09-30 13:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 13:31 [PATCH 00/17] mount: more bugfixes, the Oprah edition Christian Brauner
2026-09-30 13:31 ` [PATCH 01/17] namespace: queue a mount only once for mount notifications Christian Brauner
2026-09-30 13:31 ` [PATCH 02/17] namespace: check a submount for references right before unmounting it Christian Brauner
2026-09-30 13:31 ` [PATCH 03/17] selftests/filesystems: check that a busy submount survives a synchronous umount Christian Brauner
2026-09-30 13:44   ` sashiko-bot
2026-09-30 13:31 ` [PATCH 04/17] namespace: check a recursive bind mount for mount namespace loops Christian Brauner
2026-09-30 13:31 ` [PATCH 05/17] selftests/filesystems: check that a recursive bind mount can't pin the caller's mount namespace Christian Brauner
2026-09-30 13:31 ` [PATCH 06/17] namespace: keep covered mounts covered in OPEN_TREE_NAMESPACE Christian Brauner
2026-09-30 13:31 ` [PATCH 07/17] selftests/filesystems: check that OPEN_TREE_NAMESPACE keeps mounts covered Christian Brauner
2026-09-30 13:43   ` sashiko-bot
2026-09-30 13:32 ` [PATCH 08/17] namespace: look at the topmost mount for a mount namespace file Christian Brauner
2026-09-30 13:32 ` [PATCH 09/17] selftests/filesystems: check that a mount namespace file on top doesn't bury a mount Christian Brauner
2026-09-30 13:40   ` sashiko-bot [this message]
2026-09-30 13:32 ` [PATCH 10/17] namespace: check the mounts before reading their parents in pivot_root() Christian Brauner
2026-09-30 13:32 ` [PATCH 11/17] namespace: don't reconfigure internal superblocks via remount and umount Christian Brauner
2026-09-30 13:32 ` [PATCH 12/17] selftests/filesystems: check that the nullfs root can't be reconfigured Christian Brauner
2026-09-30 13:32 ` [PATCH 13/17] namespace: remove the fsnotify marks of a mount namespace in process context Christian Brauner
2026-09-30 15:07   ` Amir Goldstein
2026-09-30 13:32 ` [PATCH 14/17] fsnotify: detach the connector before destroying its marks Christian Brauner
2026-09-30 13:57   ` sashiko-bot
2026-10-01  9:31   ` Christian Brauner
2026-10-01 10:58     ` Amir Goldstein
2026-10-01 12:06       ` Christian Brauner
2026-09-30 13:32 ` [PATCH 15/17] dcache: don't put a mountpoint on a dentry that's being removed Christian Brauner
2026-09-30 13:32 ` [PATCH 16/17] unshare: don't drop active namespace references that were never taken Christian Brauner
2026-09-30 13:32 ` [PATCH 17/17] namespace: don't let a pseudo dentry become the root of a mount Christian Brauner

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=20260930134000.9030C1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.