[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BA3EA925-5E5E-4791-B820-83A238A2E458@kernel.org>
Date: Wed, 28 Aug 2024 22:33:23 -0700
From: Kees Cook <kees@...nel.org>
To: Xingyu Li <xli399@....edu>
CC: mcgrof@...nel.org, j.granados@...sung.com, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, Yu Hao <yhao016@....edu>,
"Paul E. McKenney" <paulmck@...nel.org>, Waiman Long <longman@...hat.com>,
Sven Eckelmann <sven@...fation.org>, Thomas Gleixner <tglx@...utronix.de>,
anna-maria@...utronix.de, frederic@...nel.org, netdev@...r.kernel.org,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Tejun Heo <tj@...nel.org>, Kuniyuki Iwashima <kuniyu@...zon.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: BUG: WARNING in retire_sysctl_set
On August 28, 2024 10:02:00 PM PDT, Xingyu Li <xli399@....edu> wrote:
>In fact, the bugs that I report are fuzzed by the syzkaller templates
>that we generated, but not those from the syzkaller official
>templates. We want to find bugs that do not have the corresponding
>official syzkaller template.
>I also checked to make sure that the bugs I reported did not occur on syzbot.
That's excellent that you've developed better templates! Can you submit these to syzkaller upstream? Then the automated fuzzing CI dashboard will benefit (and save you the work of running and reporting the new finds).
-Kees
--
Kees Cook
Powered by blists - more mailing lists