From: syzbot <syzbot+27c3c57b78da2a0995d8@syzkaller.appspotmail.com>
To: chao@kernel.org, gregkh@linuxfoundation.org, jaegeuk@kernel.org,
len.brown@intel.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, pavel@ucw.cz, rafael@kernel.org,
sandeen@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [pm?] INFO: trying to register non-static key in netdev_unregister_kobject
Date: Wed, 07 Aug 2024 12:11:05 -0700 [thread overview]
Message-ID: <000000000000fedffc061f1cabdf@google.com> (raw)
In-Reply-To: <000000000000795a2506196e7cd5@google.com>
syzbot suspects this issue was fixed by commit:
commit 54f43a10fa257ad4af02a1d157fefef6ebcfa7dc
Author: Eric Sandeen <sandeen@redhat.com>
Date: Sat Jun 29 04:38:17 2024 +0000
f2fs: remove unreachable lazytime mount option parsing
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=137e8613980000
start commit: e67572cd2204 Linux 6.9-rc6
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d2f00edef461175
dashboard link: https://syzkaller.appspot.com/bug?extid=27c3c57b78da2a0995d8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=152ab240980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13274a87180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: f2fs: remove unreachable lazytime mount option parsing
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-08-07 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 12:16 [syzbot] [pm?] INFO: trying to register non-static key in netdev_unregister_kobject syzbot
2024-08-07 19:11 ` syzbot [this message]
2024-08-08 10:37 ` Hillf Danton
2024-08-08 11:03 ` 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=000000000000fedffc061f1cabdf@google.com \
--to=syzbot+27c3c57b78da2a0995d8@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jaegeuk@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=sandeen@redhat.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