From: Yu Hao <yhao016@ucr.edu>
To: Kees Cook <kees@kernel.org>
Cc: Xingyu Li <xli399@ucr.edu>,
mcgrof@kernel.org, j.granados@samsung.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>,
Waiman Long <longman@redhat.com>,
Sven Eckelmann <sven@narfation.org>,
Thomas Gleixner <tglx@linutronix.de>,
anna-maria@linutronix.de, frederic@kernel.org,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Tejun Heo <tj@kernel.org>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: BUG: WARNING in retire_sysctl_set
Date: Wed, 28 Aug 2024 23:00:01 -0700 [thread overview]
Message-ID: <CA+UBctBGbAc5rDV97DaJGJopqTKkeuC8hHiMrN6irt84r0NoRw@mail.gmail.com> (raw)
In-Reply-To: <BA3EA925-5E5E-4791-B820-83A238A2E458@kernel.org>
On Wed, Aug 28, 2024 at 10:33 PM Kees Cook <kees@kernel.org> wrote:
> 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).
Yes, we are also working on this.
And it also takes some time to figure out the differences in the
syscall descriptions and to satisfy syzkaller's style requirements.
So we are still working on the patch of syscall descriptions for Syzkaller.
Once again, we apologize for our mistakes of some helpless report
emails and thank you for your reminder and understanding.
prev parent reply other threads:[~2024-08-29 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 21:16 BUG: WARNING in retire_sysctl_set Xingyu Li
2024-08-29 1:26 ` Kees Cook
2024-08-29 5:02 ` Xingyu Li
2024-08-29 5:33 ` Kees Cook
2024-08-29 6:00 ` Yu Hao [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=CA+UBctBGbAc5rDV97DaJGJopqTKkeuC8hHiMrN6irt84r0NoRw@mail.gmail.com \
--to=yhao016@ucr.edu \
--cc=anna-maria@linutronix.de \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=j.granados@samsung.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sven@narfation.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=xli399@ucr.edu \
/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;
as well as URLs for NNTP newsgroup(s).