public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: cheung wall <zzqq0103.hey@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: "INFO: rcu detected stall in sys_sendfile64" in Linux kernel version 6.13.0-rc2
Date: Sat, 4 Jan 2025 00:04:08 +0000	[thread overview]
Message-ID: <20250104000408.GE1977892@ZenIV> (raw)
In-Reply-To: <CAKHoSAtoy8UMwt_iXyFdrU1Zh4Q63oZb=BtjbPmJQ3zp+fxQKQ@mail.gmail.com>

On Fri, Jan 03, 2025 at 04:20:28PM +0800, cheung wall wrote:
> Hello,
> 
> I am writing to report a potential vulnerability identified in the
> Linux Kernel version 6.13.0-rc2. This issue was discovered using our
> custom vulnerability discovery tool.
> 
> HEAD commit: fac04efc5c793dccbd07e2d59af9f90b7fc0dca4 (tag: v6.13-rc2)
> 
> Detailed Call Stack:
> 
> ------------[ cut here begin]------------

Ugh...  Your tool is, by the look of it, some kind of fuzzer.
If that is correct, you really need to do a lot of things
for it to be useful.

"Something done by my userland code has ended up with this spew into
kernel log" _may_ be of use in some cases, but examples you've posted
are not of that sort.

The things missing:
	* what _was_ done by the userland to trigger that?
	* how reproducible it is?
	* which commit (if any) has introduced that behaviour?
Might or might not be available, but "bump the version number to
6.13-rc2" is very unlikely to be it.
	* can the reproducer (if available) be trimmed down?

You really would be better off if you described what that tool is
trying to do and what are your plans for it - missing parts, etc.

As it is, you are dumping a stream of low-quality output on people
who are not in position to do anything useful with it.  In effect,
you are training everyone to ignore anything you post, which is
probably not the desired result.

      reply	other threads:[~2025-01-04  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03  8:20 "INFO: rcu detected stall in sys_sendfile64" in Linux kernel version 6.13.0-rc2 cheung wall
2025-01-04  0:04 ` Al Viro [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=20250104000408.GE1977892@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zzqq0103.hey@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox