From: Roman Gushchin <roman.gushchin@linux.dev>
To: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
Cc: sashiko@lists.linux.dev
Subject: Re: Execution with sanitizers, integration with syzkaller
Date: Thu, 16 Jul 2026 16:18:50 +0000 [thread overview]
Message-ID: <7ia47bmusyad.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <CACzwLxgcbUXHpLZi3fz1iyjDY_kp69X4dEnObwg7wEqKdVejXg@mail.gmail.com> (Sabyrzhan Tasbolatov's message of "Thu, 16 Jul 2026 16:23:49 +0500")
Sabyrzhan Tasbolatov <snovitoll@gmail.com> writes:
> Hello,
>
> Thanks for the amazing project!
Thanks!
> From https://github.com/sashiko-dev/sashiko README.md:
>
>> Stage 3: Execution flow verification. Traces C code execution flow,
>> checking for logic errors, missing return checks, unhandled error paths,
>> and off-by-one errors.
>
> I wonder if sashiko's Stage 3 can be configured or altered
> with KASAN, KMSAN etc. sanitizers. I couldn't find how the execution works.
> Perhaps, such as sanitizers could improve the PATCH review,
> as the optional flag during Stage 3.
Do you mean actually build and run the kernel?
If so, it's not what I want to build into Sashiko directly, because
it will require significant infrastructure, a lot of hardware and
corresponding support and will complicate things a lot. However there
will be a database of pre-existing kernel bugs open to other trusted
tools (e.g. syzkaller) which will be able to enrich ai findings.
> This also brings up a vague thought about sashiko + syzkaller projects,
> where sashiko could provide information about the similar bugs found
> in the PATCH, if any, among syzkaller reports. Like adding syzkaller
> mailing list
> reports as context as well.
Sorry, not sure I got your idea. Can you elaborate please?
Thanks!
prev parent reply other threads:[~2026-07-16 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 11:23 Execution with sanitizers, integration with syzkaller Sabyrzhan Tasbolatov
2026-07-16 16:18 ` Roman Gushchin [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=7ia47bmusyad.fsf@castle.c.googlers.com \
--to=roman.gushchin@linux.dev \
--cc=sashiko@lists.linux.dev \
--cc=snovitoll@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