From: Borislav Petkov <bp@alien8.de>
To: syzbot <syzbot+81e6ff9d4cdb05fd4f5e@syzkaller.appspotmail.com>
Cc: adobriyan@gmail.com, ak@linux.intel.com, bigeasy@linutronix.de,
fenghua.yu@intel.com, frederic@kernel.org, hpa@zytor.com,
keescook@chromium.org, kernelfans@gmail.com, len.brown@intel.com,
linux-kernel@vger.kernel.org, longman@redhat.com,
luto@kernel.org, mingo@redhat.com, peterz@infradead.org,
rafael.j.wysocki@intel.com, riel@surriel.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tim.c.chen@linux.intel.com, tonywwang-oc@zhaoxin.com,
wang.yi59@zte.com.cn, x86@kernel.org
Subject: Re: general protection fault in tss_update_io_bitmap
Date: Thu, 21 Nov 2019 12:01:15 +0100 [thread overview]
Message-ID: <20191121110115.GC6540@zn.tnic> (raw)
In-Reply-To: <0000000000004dccce0597d1967b@google.com>
On Wed, Nov 20, 2019 at 05:55:09PM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 5d1131b4 Add linux-next specific files for 20191119
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=177979d2e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=b60c562d89e5a8df
> dashboard link: https://syzkaller.appspot.com/bug?extid=81e6ff9d4cdb05fd4f5e
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1549ed8ce00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17f91012e00000
>
> The bug was bisected to:
>
> commit 111e7b15cf10f6e973ccf537c70c66a5de539060
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Tue Nov 12 20:40:33 2019 +0000
>
> x86/ioperm: Extend IOPL config to control ioperm() as well
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10490e86e00000
> final crash: https://syzkaller.appspot.com/x/report.txt?x=12490e86e00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=14490e86e00000
Try this:
https://git.kernel.org/tip/e3cb0c7102f04c83bf1a7cb1d052e92749310b46
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2019-11-21 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 1:55 general protection fault in tss_update_io_bitmap syzbot
2019-11-21 11:01 ` Borislav Petkov [this message]
2019-11-21 17:36 ` Kees Cook
2019-11-21 20:19 ` syzbot
2019-11-22 9:30 ` Borislav Petkov
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=20191121110115.GC6540@zn.tnic \
--to=bp@alien8.de \
--cc=adobriyan@gmail.com \
--cc=ak@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=fenghua.yu@intel.com \
--cc=frederic@kernel.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kernelfans@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=riel@surriel.com \
--cc=syzbot+81e6ff9d4cdb05fd4f5e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=tonywwang-oc@zhaoxin.com \
--cc=wang.yi59@zte.com.cn \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox