From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@redhat.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
joamaki@gmail.com, haliu@redhat.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org
Subject: Re: [PATCH] bpf/selftests: Fix namespace mount setup in tc_redirect
Date: Wed, 05 Jan 2022 12:40:16 +0000 [thread overview]
Message-ID: <164138641619.6231.12315835333755803519.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220104121030.138216-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 4 Jan 2022 13:10:30 +0100 you wrote:
> The tc_redirect umounts /sys in the new namespace, which can be
> mounted as shared and cause global umount. The lazy umount also
> takes down mounted trees under /sys like debugfs, which won't be
> available after sysfs mounts again and could cause fails in other
> tests.
>
> # cat /proc/self/mountinfo | grep debugfs
> 34 23 0:7 / /sys/kernel/debug rw,nosuid,nodev,noexec,relatime shared:14 - debugfs debugfs rw
> # cat /proc/self/mountinfo | grep sysfs
> 23 86 0:22 / /sys rw,nosuid,nodev,noexec,relatime shared:2 - sysfs sysfs rw
> # mount | grep debugfs
> debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
>
> [...]
Here is the summary with links:
- bpf/selftests: Fix namespace mount setup in tc_redirect
https://git.kernel.org/bpf/bpf-next/c/5e22dd186267
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-01-05 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 12:10 [PATCH] bpf/selftests: Fix namespace mount setup in tc_redirect Jiri Olsa
2022-01-05 12:40 ` patchwork-bot+netdevbpf [this message]
2022-01-05 20:40 ` Andrii Nakryiko
2022-01-06 7:35 ` Jiri Olsa
2022-01-17 19:25 ` Jiri Olsa
2022-01-19 3:48 ` Andrii Nakryiko
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=164138641619.6231.12315835333755803519.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haliu@redhat.com \
--cc=joamaki@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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.