From: syzbot <syzbot+d2c31705e468a347e6db@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in netdev_register_kobject
Date: Thu, 31 Aug 2023 04:22:34 -0700 [thread overview]
Message-ID: <000000000000bc839e060436421f@google.com> (raw)
In-Reply-To: <20230831105150.4549-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+d2c31705e468a347e6db@syzkaller.appspotmail.com
Tested on:
commit: a47fc304 Add linux-next specific files for 20230831
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1716e99fa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8294f0401243efe1
dashboard link: https://syzkaller.appspot.com/bug?extid=d2c31705e468a347e6db
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=10a4e470680000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-08-31 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230831105150.4549-1-hdanton@sina.com>
2023-08-31 11:22 ` syzbot [this message]
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
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=000000000000bc839e060436421f@google.com \
--to=syzbot+d2c31705e468a347e6db@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.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 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).