[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZPHS4Ps3dszk/5m0@smile.fi.intel.com>
Date: Fri, 1 Sep 2023 15:02:40 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: syzbot <syzbot+d2c31705e468a347e6db@...kaller.appspotmail.com>,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
rafael@...nel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in
netdev_register_kobject
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@...ux.intel.com> wrote:
> > On Thu, Aug 31, 2023 at 05:53:29PM +0200, Aleksandr Nogikh wrote:
...
> > JFYI:
> > 20230828145824.3895288-1-andriy.shevchenko@...ux.intel.com
> >
> > Can be used for testing.
> > So I like to write
> >
> > #syz test patch: 20230828145824.3895288-1-andriy.shevchenko@...ux.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
Powered by blists - more mailing lists