From: Josh Poimboeuf <jpoimboe@redhat.com>
To: syzbot <syzbot+e73ceacfd8560cc8a3ca@syzkaller.appspotmail.com>
Cc: bp@alien8.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, netdev@vger.kernel.org, peterz@infradead.org,
shile.zhang@linux.alibaba.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: BUG: stack guard page was hit in unwind_next_frame
Date: Mon, 4 May 2020 14:03:48 -0500 [thread overview]
Message-ID: <20200504190348.iphzmd7micvidh46@treble> (raw)
In-Reply-To: <0000000000005a8fe005a4b8a114@google.com>
On Sat, May 02, 2020 at 11:36:11PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 8999dc89 net/x25: Fix null-ptr-deref in x25_disconnect
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=16004440100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=b7a70e992f2f9b68
> dashboard link: https://syzkaller.appspot.com/bug?extid=e73ceacfd8560cc8a3ca
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+e73ceacfd8560cc8a3ca@syzkaller.appspotmail.com
Infinite loop in network code.
#syz dup: BUG: stack guard page was hit in deref_stack_reg
--
Josh
next prev parent reply other threads:[~2020-05-04 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 6:36 BUG: stack guard page was hit in unwind_next_frame syzbot
2020-05-04 19:03 ` Josh Poimboeuf [this message]
2020-05-05 1:06 ` Cong Wang
2020-05-05 7:02 ` Cong Wang
[not found] ` <20200503102220.3848-1-hdanton@sina.com>
2020-05-07 9:59 ` Dan Carpenter
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=20200504190348.iphzmd7micvidh46@treble \
--to=jpoimboe@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=shile.zhang@linux.alibaba.com \
--cc=syzbot+e73ceacfd8560cc8a3ca@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).