From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+d2c31705e468a347e6db@syzkaller.appspotmail.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in netdev_register_kobject
Date: Fri, 1 Sep 2023 15:02:40 +0300 [thread overview]
Message-ID: <ZPHS4Ps3dszk/5m0@smile.fi.intel.com> (raw)
In-Reply-To: <CANp29Y5Bq1fo8pFWGxKT9NTNW_-C6vf=A_hUKG2BJey5JRrO1g@mail.gmail.com>
On Fri, Sep 01, 2023 at 01:07:20PM +0200, Aleksandr Nogikh wrote:
> On Thu, Aug 31, 2023 at 6:33 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, Aug 31, 2023 at 05:53:29PM +0200, Aleksandr Nogikh wrote:
...
> > JFYI:
> > 20230828145824.3895288-1-andriy.shevchenko@linux.intel.com
> >
> > Can be used for testing.
> > So I like to write
> >
> > #syz test patch: 20230828145824.3895288-1-andriy.shevchenko@linux.intel.com
>
> Thanks for the idea!
> I've filed https://github.com/google/syzkaller/issues/4182
>
> The biggest problem is to figure out the command syntax that'd also
> let us specify the tree on which to apply the patch. Or to restrict
> the patch testing to either apply the patch from lore on top of the
> fuzzed tree or to accept repo/branch/patch explicitly.
Ah, that's easy to solve. I've commented there.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-09-01 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 7:05 [syzbot] [kernel?] general protection fault in netdev_register_kobject syzbot
2023-08-31 14:11 ` Andy Shevchenko
2023-08-31 14:13 ` syzbot
[not found] ` <CANp29Y5GFuGe9=kBp-xmTb8tesLY4oAjewZ5c_31jmf8+AocBQ@mail.gmail.com>
2023-08-31 15:39 ` Andy Shevchenko
2023-08-31 15:53 ` Aleksandr Nogikh
2023-08-31 16:33 ` Andy Shevchenko
2023-08-31 16:33 ` syzbot
2023-09-01 11:07 ` Aleksandr Nogikh
2023-09-01 12:02 ` Andy Shevchenko [this message]
[not found] <20230831105150.4549-1-hdanton@sina.com>
2023-08-31 11:22 ` syzbot
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=ZPHS4Ps3dszk/5m0@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=rafael@kernel.org \
--cc=syzbot+d2c31705e468a347e6db@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).