From: Luis Chamberlain <mcgrof@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Christoph Hellwig <hch@infradead.org>,
mcgrof@kernel.org
Cc: syzbot <syzbot+46c77dc7e98c732de754@syzkaller.appspotmail.com>,
dhowells@redhat.com, jarkko.sakkinen@linux.intel.com,
jmorris@namei.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, serge@hallyn.com,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in request_key_tag
Date: Wed, 01 Jul 2020 12:20:30 +0000 [thread overview]
Message-ID: <20200701122030.GP4332@42.do-not-panic.com> (raw)
In-Reply-To: <728915db-592b-997f-6970-464cc59441d7@i-love.sakura.ne.jp>
On Wed, Jul 01, 2020 at 07:04:15PM +0900, Tetsuo Handa wrote:
> 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.
That patch has been dropped for now due to another reported issue
bisected to it and even though we have not root caused that issue [0].
It would be good to have a reproducer for this reported issue as well,
but I should also point out a regression which Naresh reported is fixed
recently by a posted patch [1] by Herbert Xu. It would be good if you
can test with that patch posted by Herbert.
[0] https://lkml.kernel.org/r/20200623141157.5409-1-borntraeger@de.ibm.com
[1] https://lkml.kernel.org/r/20200626062948.GA25285@gondor.apana.org.au
Luis
>
> 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\x17925a9d100000
> > kernel config: https://syzkaller.appspot.com/x/.config?xÜd26bbca17dd1db
> > dashboard link: https://syzkaller.appspot.com/bug?extidFc77dc7e98c732de754
> > 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@syzkaller.appspotmail.com
WARNING: multiple messages have this Message-ID (diff)
From: Luis Chamberlain <mcgrof@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Christoph Hellwig <hch@infradead.org>,
mcgrof@kernel.org
Cc: syzbot <syzbot+46c77dc7e98c732de754@syzkaller.appspotmail.com>,
dhowells@redhat.com, jarkko.sakkinen@linux.intel.com,
jmorris@namei.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, serge@hallyn.com,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in request_key_tag
Date: Wed, 1 Jul 2020 12:20:30 +0000 [thread overview]
Message-ID: <20200701122030.GP4332@42.do-not-panic.com> (raw)
In-Reply-To: <728915db-592b-997f-6970-464cc59441d7@i-love.sakura.ne.jp>
On Wed, Jul 01, 2020 at 07:04:15PM +0900, Tetsuo Handa wrote:
> 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.
That patch has been dropped for now due to another reported issue
bisected to it and even though we have not root caused that issue [0].
It would be good to have a reproducer for this reported issue as well,
but I should also point out a regression which Naresh reported is fixed
recently by a posted patch [1] by Herbert Xu. It would be good if you
can test with that patch posted by Herbert.
[0] https://lkml.kernel.org/r/20200623141157.5409-1-borntraeger@de.ibm.com
[1] https://lkml.kernel.org/r/20200626062948.GA25285@gondor.apana.org.au
Luis
>
> 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@syzkaller.appspotmail.com
next prev parent reply other threads:[~2020-07-01 12:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 7:53 INFO: task hung in request_key_tag syzbot
2020-07-01 7:53 ` syzbot
2020-07-01 10:04 ` Tetsuo Handa
2020-07-01 10:04 ` Tetsuo Handa
2020-07-01 12:20 ` Luis Chamberlain [this message]
2020-07-01 12:20 ` Luis Chamberlain
2020-07-01 12:49 ` Tetsuo Handa
2020-07-01 12:49 ` Tetsuo Handa
2020-07-03 11:40 ` syzbot
2020-07-03 11:40 ` 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=20200701122030.GP4332@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hch@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=serge@hallyn.com \
--cc=syzbot+46c77dc7e98c732de754@syzkaller.appspotmail.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 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.