[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <728915db-592b-997f-6970-464cc59441d7@i-love.sakura.ne.jp>
Date: Wed, 1 Jul 2020 19:04:15 +0900
From: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: syzbot <syzbot+46c77dc7e98c732de754@...kaller.appspotmail.com>,
dhowells@...hat.com, jarkko.sakkinen@...ux.intel.com,
jmorris@...ei.org, keyrings@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, serge@...lyn.com,
syzkaller-bugs@...glegroups.com
Subject: Re: INFO: task hung in request_key_tag
I suspect commit 9e9b47d6bbe9df65 ("umh: fix processed error when UMH_WAIT_PROC is used").
Maybe the change in kernel/umh.c and/or security/keys/request_key.c made by that commit is
affecting call_usermodehelper_keys() == 0 case when complete_request_key() is called.
On 2020/07/01 16:53, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: c28e58ee Add linux-next specific files for 20200629
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=17925a9d100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=dcd26bbca17dd1db
> dashboard link: https://syzkaller.appspot.com/bug?extid=46c77dc7e98c732de754
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+46c77dc7e98c732de754@...kaller.appspotmail.com
Powered by blists - more mailing lists