From: Kees Cook <keescook@chromium.org>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
syzbot <syzbot+7ffc7214b893651d52b8@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com,
Andy Lutomirski <luto@kernel.org>
Subject: Re: WARNING in syscall_exit_to_user_mode
Date: Sat, 12 Sep 2020 10:52:52 -0700 [thread overview]
Message-ID: <202009121050.0D9CAB95@keescook> (raw)
In-Reply-To: <00000000000018a47605af074c7d@google.com>
On Fri, Sep 11, 2020 at 03:39:19AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: f4d51dff Linux 5.9-rc4
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12a4e7cd900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a9075b36a6ae26c9
> dashboard link: https://syzkaller.appspot.com/bug?extid=7ffc7214b893651d52b8
> compiler: gcc (GCC) 10.1.0-syz 20200507
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=122d7335900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13cea1a5900000
>
> Bisection is inconclusive: the issue happens on the oldest tested release.
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=162247cd900000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=152247cd900000
> console output: https://syzkaller.appspot.com/x/log.txt?x=112247cd900000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+7ffc7214b893651d52b8@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> syscall 56 left IRQs disabled
This WARN appears reachable. :)
I also see on the dashboard these other problems with the new entry
code:
https://syzkaller.appspot.com/bug?extid=d4336c84ed0099fdbe47
https://syzkaller.appspot.com/bug?extid=c4af95386364bc59b13e
I can't tell if any of these have been looked at yet, though.
--
Kees Cook
next prev parent reply other threads:[~2020-09-12 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 10:39 WARNING in syscall_exit_to_user_mode syzbot
2020-09-12 17:52 ` Kees Cook [this message]
2020-09-13 19:54 ` Thomas Gleixner
2020-09-14 20:06 ` Kees Cook
2020-09-14 20:22 ` Thomas Gleixner
2020-09-13 19:40 ` Thomas Gleixner
2020-11-08 17:22 ` syzbot
2020-11-11 11:11 ` Dmitry Vyukov
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=202009121050.0D9CAB95@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=syzbot+7ffc7214b893651d52b8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.