From: Josh Poimboeuf <jpoimboe@redhat.com>
To: syzbot <syzbot+2a3c14db0e17fe4c7409@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 deref_stack_reg
Date: Sun, 15 Mar 2020 09:49:19 -0500 [thread overview]
Message-ID: <20200315144919.y6r5sarg5m4s6wpw@treble> (raw)
In-Reply-To: <000000000000f5a6bf05a0ce0a95@google.com>
On Sat, Mar 14, 2020 at 03:28:11AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 34a568a2 net: sgi: ioc3-eth: Remove phy workaround
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=103e69fde00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=598678fc6e800071
> dashboard link: https://syzkaller.appspot.com/bug?extid=2a3c14db0e17fe4c7409
> 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+2a3c14db0e17fe4c7409@syzkaller.appspotmail.com
This is a stack overflow caused by a recursive loop in the networking
code. This chain repeats until it runs out of stack:
> bond_compute_features.isra.0+0x521/0xa40 drivers/net/bonding/bond_main.c:1188
> bond_slave_netdev_event drivers/net/bonding/bond_main.c:3237 [inline]
> bond_netdev_event+0x6ee/0x930 drivers/net/bonding/bond_main.c:3277
> notifier_call_chain+0xc0/0x230 kernel/notifier.c:83
> call_netdevice_notifiers_info net/core/dev.c:1948 [inline]
> call_netdevice_notifiers_info+0xb5/0x130 net/core/dev.c:1933
> call_netdevice_notifiers_extack net/core/dev.c:1960 [inline]
> call_netdevice_notifiers net/core/dev.c:1974 [inline]
> netdev_features_change net/core/dev.c:1364 [inline]
> netdev_update_features net/core/dev.c:9082 [inline]
> netdev_update_features+0xc4/0xd0 net/core/dev.c:9079
> netdev_sync_lower_features net/core/dev.c:8891 [inline]
> __netdev_update_features+0x821/0x12f0 net/core/dev.c:9026
> netdev_change_features+0x61/0xb0 net/core/dev.c:9098
> bond_compute_features.isra.0+0x521/0xa40 drivers/net/bonding/bond_main.c:1188
--
Josh
prev parent reply other threads:[~2020-03-15 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 10:28 BUG: stack guard page was hit in deref_stack_reg syzbot
2020-03-15 14:49 ` Josh Poimboeuf [this message]
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=20200315144919.y6r5sarg5m4s6wpw@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+2a3c14db0e17fe4c7409@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