public inbox for linux-kernel@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: "WARNING in max_vclocks_store" in Linux kernel version 6.13.0-rc2
Date: Fri, 3 Jan 2025 09:19:06 +0000	[thread overview]
Message-ID: <20250103091906.GD1977892@ZenIV> (raw)
In-Reply-To: <CAKHoSAu3D+s_jzquKrR2YXFd_gNMu5AfDg7_+HjYEtyCSwJ-4g@mail.gmail.com>

On Fri, Jan 03, 2025 at 04:19:35PM +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:

Out of curiosity, what would you expect any of us to be able to do with that
information, given that we
	* have no information about that tool of yours
	* have no idea how to interpret those call chains
	* have no way to compare those for different commits
etc?

Seriously, step back and imagine somebody with zero information about your tool
staring at the email you've sent.

Al, completely bewildered...

  reply	other threads:[~2025-01-03  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03  8:19 "WARNING in max_vclocks_store" in Linux kernel version 6.13.0-rc2 cheung wall
2025-01-03  9:19 ` Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-03  7:50 cheung wall

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=20250103091906.GD1977892@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