From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Zihan Xi <zihanx@nebusec.ai>
Cc: Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH nf 0/1] netfilter: x_tables: avoid holding mutex over faultable user copies
Date: Wed, 9 Sep 2026 02:52:22 +0200 [thread overview]
Message-ID: <aqCtxhu5Av_RLtY8@chamomile> (raw)
In-Reply-To: <cover.1788244146.git.zihanx@nebusec.ai>
On Tue, Sep 01, 2026 at 01:47:53PM +0000, Zihan Xi wrote:
[...]
> Reproducer:
>
> The following files must be saved with these exact names in one directory.
> The commands below build all helpers and run the FUSE/user-namespace path.
> The FUSE helper binary is named poc-userns-trig so the hung-task comm
> matches the crash log. The captured panic is hung_task after that task
> blocked for more than 10 seconds, and then khungtaskd panics because
> hung_task_panic=1. A 10-second timeout alone only warns; it does not
> panic. The tested guest enabled panic on the kernel command line with
> hung_task_panic=1 hung_task_timeout_secs=10
> hung_task_check_interval_secs=10 panic=-1. poc.sh, poc-userns-trig and
> poc.c also write these sysctls when they are writable:
>
> echo 10 > /proc/sys/kernel/hung_task_timeout_secs
> echo 10 > /proc/sys/kernel/hung_task_check_interval_secs
> echo 10 > /proc/sys/kernel/hung_task_warnings
> echo 1 > /proc/sys/kernel/hung_task_panic
This configuration does not look sensible to me.
prev parent reply other threads:[~2026-09-09 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 13:47 Zihan Xi
2026-09-01 13:47 ` [PATCH nf 1/1] " Zihan Xi
2026-09-09 0:52 ` Pablo Neira Ayuso [this message]
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=aqCtxhu5Av_RLtY8@chamomile \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phil@nwl.cc \
--cc=zihanx@nebusec.ai \
/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
all inboxes | Powered by JetHome®