From: syzbot <syzbot+b9bd12fbed3485a3e51f@syzkaller.appspotmail.com>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: gregkh@linuxfoundation.org, len.brown@intel.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
paskripkin@gmail.com, pavel@ucw.cz, rafael@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in __pm_runtime_resume (2)
Date: Sun, 13 Mar 2022 10:27:58 -0700 [thread overview]
Message-ID: <00000000000093a3f805da1ce2f7@google.com> (raw)
In-Reply-To: <79d2c7e0-c4ed-fa89-5d97-4b143356f814@gmail.com>
> On 3/13/22 08:35, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 92f90cc9fe0e Merge tag 'fuse-fixes-5.17-rc8' of git://git...
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=118cd3be700000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=442f8ac61e60a75e
>> dashboard link: https://syzkaller.appspot.com/bug?extid=b9bd12fbed3485a3e51f
>> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b64e79700000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1652811a700000
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+b9bd12fbed3485a3e51f@syzkaller.appspotmail.com
>>
>
> hu->serdev should be checked before passing to pm functions
>
> #syz test:
want 2 args (repo, branch), got 3
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>
>
>
>
>
> With regards,
> Pavel Skripkin
next prev parent reply other threads:[~2022-03-13 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 5:35 [syzbot] general protection fault in __pm_runtime_resume (2) syzbot
2022-03-13 17:27 ` Pavel Skripkin
2022-03-13 17:27 ` syzbot [this message]
2022-03-13 17:29 ` Pavel Skripkin
2022-03-13 17:41 ` syzbot
2022-03-13 17:27 ` 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=00000000000093a3f805da1ce2f7@google.com \
--to=syzbot+b9bd12fbed3485a3e51f@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=pavel@ucw.cz \
--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.