From: Eduard Zingerman <eddyz87@gmail.com>
To: Amery Hung <ameryhung@gmail.com>, bpf@vger.kernel.org
Cc: daniel@iogearbox.net, andrii@kernel.org,
alexei.starovoitov@gmail.com, martin.lau@kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next v5 3/3] selftests/bpf: Fix dangling stdout seen by traffic monitor thread
Date: Wed, 05 Mar 2025 13:43:35 -0800 [thread overview]
Message-ID: <317f9cbed81d6178b167efbc796ed1fc1bfa07a6.camel@gmail.com> (raw)
In-Reply-To: <20250305182057.2802606-3-ameryhung@gmail.com>
On Wed, 2025-03-05 at 10:20 -0800, Amery Hung wrote:
> Traffic monitor thread may see dangling stdout as the main thread closes
> and reassigns stdout without protection. This happens when the main thread
> finishes one subtest and moves to another one in the same netns_new()
> scope.
>
> The issue can be reproduced by running test_progs repeatedly with traffic
> monitor enabled:
>
> for ((i=1;i<=100;i++)); do
> ./test_progs -a flow_dissector_skb* -m '*'
> done
>
> For restoring stdout in crash_handler(), since it does not really care
> about closing stdout, simlpy flush stdout and restore it to the original
> one.
>
> Then, Fix the issue by consolidating stdio_restore_cleanup() and
> stdio_restore(), and protecting the use/close/assignment of stdout with
> a lock. The locking in the main thread is always performed regradless of
> whether traffic monitor is running or not for simplicity. It won't have
> any side-effect.
>
> Signed-off-by: Amery Hung <ameryhung@gmail.com>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
[...]
next prev parent reply other threads:[~2025-03-05 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 18:20 [PATCH bpf-next v5 1/3] selftests/bpf: Clean up call sites of stdio_restore() Amery Hung
2025-03-05 18:20 ` [PATCH bpf-next v5 2/3] selftests/bpf: Allow assigning traffic monitor print function Amery Hung
2025-03-05 18:20 ` [PATCH bpf-next v5 3/3] selftests/bpf: Fix dangling stdout seen by traffic monitor thread Amery Hung
2025-03-05 21:43 ` Eduard Zingerman [this message]
2025-03-05 21:42 ` [PATCH bpf-next v5 1/3] selftests/bpf: Clean up call sites of stdio_restore() Eduard Zingerman
2025-03-06 22:20 ` patchwork-bot+netdevbpf
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=317f9cbed81d6178b167efbc796ed1fc1bfa07a6.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox