From: syzbot <syzbot+81e6ff9d4cdb05fd4f5e@syzkaller.appspotmail.com>
To: adobriyan@gmail.com, ak@linux.intel.com, bigeasy@linutronix.de,
bp@alien8.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:19:01 -0800 [thread overview]
Message-ID: <0000000000000a7dfc0597e10206@google.com> (raw)
In-Reply-To: <201911210931.DB5346C8@keescook>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+81e6ff9d4cdb05fd4f5e@syzkaller.appspotmail.com
Tested on:
commit: e3cb0c71 x86/ioperm: Fix use of deprecated config option
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
kernel config: https://syzkaller.appspot.com/x/.config?x=1fc51b2845bfe6fc
dashboard link: https://syzkaller.appspot.com/bug?extid=81e6ff9d4cdb05fd4f5e
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2019-11-21 20:19 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
2019-11-21 17:36 ` Kees Cook
2019-11-21 20:19 ` syzbot [this message]
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=0000000000000a7dfc0597e10206@google.com \
--to=syzbot+81e6ff9d4cdb05fd4f5e@syzkaller.appspotmail.com \
--cc=adobriyan@gmail.com \
--cc=ak@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.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=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 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.