From: syzbot <syzbot+7ffc7214b893651d52b8@syzkaller.appspotmail.com>
To: b.zolnierkie@samsung.com, christian@brauner.io,
dan.carpenter@oracle.com, george.kennedy@oracle.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
luto@kernel.org, mingo@kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: WARNING in syscall_exit_to_user_mode
Date: Sun, 08 Nov 2020 09:22:07 -0800 [thread overview]
Message-ID: <0000000000006942a305b39baf75@google.com> (raw)
In-Reply-To: <00000000000018a47605af074c7d@google.com>
syzbot suspects this issue was fixed by commit:
commit a49145acfb975d921464b84fe00279f99827d816
Author: George Kennedy <george.kennedy@oracle.com>
Date: Tue Jul 7 19:26:03 2020 +0000
fbmem: add margin check to fb_check_caps()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17a21f32500000
start commit: f4d51dff Linux 5.9-rc4
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a9075b36a6ae26c9
dashboard link: https://syzkaller.appspot.com/bug?extid=7ffc7214b893651d52b8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=122d7335900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13cea1a5900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fbmem: add margin check to fb_check_caps()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-11-08 17:22 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
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 [this message]
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=0000000000006942a305b39baf75@google.com \
--to=syzbot+7ffc7214b893651d52b8@syzkaller.appspotmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=christian@brauner.io \
--cc=dan.carpenter@oracle.com \
--cc=george.kennedy@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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.