All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d2c31705e468a347e6db@syzkaller.appspotmail.com>
To: andriy.shevchenko@linux.intel.com
Cc: andriy.shevchenko@linux.intel.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, nogikh@google.com,
	rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in netdev_register_kobject
Date: Thu, 31 Aug 2023 09:33:41 -0700	[thread overview]
Message-ID: <00000000000060e52d06043a9b7b@google.com> (raw)
In-Reply-To: <ZPDA1Z8Hwq3jdvgh@smile.fi.intel.com>

> On Thu, Aug 31, 2023 at 05:53:29PM +0200, Aleksandr Nogikh wrote:
>> On Thu, Aug 31, 2023 at 5:39 PM Andy Shevchenko
>> <andriy.shevchenko@linux.intel.com> wrote:
>> > On Thu, Aug 31, 2023 at 04:15:23PM +0200, Aleksandr Nogikh wrote:
>> > > #syz dup: general protection fault in nfc_register_device
>> >
>> > Thanks!
>> >
>> > Maybe you can improve it to
>> > 1) drop those prefixes by itself;
>> 
>> Yeah, I've just thought about it too when I was correcting the command.
>> 
>> > 2) explain better in the quick help below what "exact" means.
>> >
>> > Also is it possible to test just patches without repository?
>> > Can you add this feature when you simply submit a message ID
>> > to it and it uses lore.kernel.org for the patch or series?
>> 
>> Thanks, these are good suggestions!
>> The first one is easy to do (we actually already support that
>> internally, so only a small change is needed), the second one is a bit
>> trickier, but I'll look into that.
>
> 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

"patch:" does not look like a valid git repo address.

>
> The responses can be (among others?):
> 1/ tested and test results;
> 2/ not found.
>
> -- 
> With Best Regards,
> Andy Shevchenko
>
>

  reply	other threads:[~2023-08-31 16:33 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 [this message]
2023-09-01 11:07             ` Aleksandr Nogikh
2023-09-01 12:02               ` Andy Shevchenko
     [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=00000000000060e52d06043a9b7b@google.com \
    --to=syzbot+d2c31705e468a347e6db@syzkaller.appspotmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nogikh@google.com \
    --cc=rafael@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.