From: Kees Cook <kees@kernel.org>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: sashiko <sashiko@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Chris Mason <mason@kernel.org>, Jason Gunthorpe <jgg@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: sashiko & pre-existing bugs
Date: Thu, 17 Sep 2026 21:25:23 -0700 [thread overview]
Message-ID: <202609172122.425EFBD9@keescook> (raw)
In-Reply-To: <7ia4se37qwvk.fsf@castle.c.googlers.com>
On Thu, Sep 17, 2026 at 11:30:23PM +0000, Roman Gushchin wrote:
> as some of you might notice, a couple of days ago sashiko stopped to
> report preexisting bugs together with not-yet-introduced new issues.
> Instead, it started putting them into the database. All M: and R: in the
> current MAINTAINERS file have full access to corresponding bugs.
>
> There is a new "Bugs" button in the top right corner which is the access
> to the database. You don't need to create an account, invent a password,
> etc. It's all stateless.
>
> If you're working on other tools which discover linux kernel issues
> and/or can generate reproducers/fix candidates and want to collaborate,
> please, reach out to me.
Oh cool! That worked very nicely; I'm all logged in and cringing at the
lists. ;)
--
Kees Cook
next prev parent reply other threads:[~2026-09-18 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 23:30 sashiko & pre-existing bugs Roman Gushchin
2026-09-18 4:25 ` Kees Cook [this message]
2026-10-02 23:34 ` Alison Schofield
2026-10-03 20:10 ` Roman Gushchin
2026-10-03 17:24 ` SJ Park
2026-10-03 18:09 ` SJ Park
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=202609172122.425EFBD9@keescook \
--to=kees@kernel.org \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=sashiko@lists.linux.dev \
/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.