From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+05fc3a636f5ee8830a99@syzkaller.appspotmail.com>
Cc: Chris von Recklinghausen <crecklin@redhat.com>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: stack-out-of-bounds Read in check_stack_object
Date: Sun, 6 Jan 2019 23:37:45 +0900 [thread overview]
Message-ID: <40577a65-3947-aec9-3b82-ac71f150e586@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <CACT4Y+Y+dph0wyKOLffXMPFPsvbviYzfn1nrJJgOL1ngkQLtVw@mail.gmail.com>
On 2019/01/06 22:48, Dmitry Vyukov wrote:
> On Sun, Jan 6, 2019 at 2:31 PM syzbot
> <syzbot+05fc3a636f5ee8830a99@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit: 3fed6ae4b027 ia64: fix compile without swiotlb
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=161ce1d7400000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=7308e68273924137
>> dashboard link: https://syzkaller.appspot.com/bug?extid=05fc3a636f5ee8830a99
>> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>> userspace arch: i386
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b3769f400000
>>
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+05fc3a636f5ee8830a99@syzkaller.appspotmail.com
>
> I suspect this is another incarnation of:
> https://syzkaller.appspot.com/bug?id=4821de869e3d78a255a034bf212a4e009f6125a7
> Any other ideas?
>> CPU: 0 PID: -1455013312 Comm: Not tainted 4.20.0+ #10
"current->pid < 0" suggests that "struct task_struct" was overwritten.
>> #PF error: [normal kernel read fault]
>> Thread overran stack, or stack corrupted
And "struct task_struct" might be overwritten by stack overrun?
The cause of overrun is unknown, but given that
"fou6: Prevent unbounded recursion in GUE error handler" is not yet
applied to linux.git tree, this might be a dup of that bug.
next prev parent reply other threads:[~2019-01-06 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 13:31 syzbot
2019-01-06 13:31 ` syzbot
2019-01-06 13:48 ` Dmitry Vyukov
2019-01-06 13:48 ` Dmitry Vyukov
2019-01-06 14:37 ` Tetsuo Handa [this message]
2019-01-06 15:44 ` Dmitry Vyukov
2019-01-06 15:44 ` 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=40577a65-3947-aec9-3b82-ac71f150e586@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=crecklin@redhat.com \
--cc=dvyukov@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+05fc3a636f5ee8830a99@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox