From: Jiri Pirko <jiri@resnulli.us>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+60748c96cf5c6df8e581@syzkaller.appspotmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel panic: kernel stack overflow
Date: Wed, 12 Oct 2022 15:11:15 +0200 [thread overview]
Message-ID: <Y0a88zDFLVeVzBPB@nanopsycho> (raw)
In-Reply-To: <CACT4Y+Zuoo_rgf=DP90wgSVm909Qboj5kdYQjZELPDfdkQWJqA@mail.gmail.com>
Wed, Oct 12, 2022 at 09:53:27AM CEST, dvyukov@google.com wrote:
>On Wed, 12 Oct 2022 at 09:48, syzbot
><syzbot+60748c96cf5c6df8e581@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: bbed346d5a96 Merge branch 'for-next/core' into for-kernelci
>> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
>> console output: https://syzkaller.appspot.com/x/log.txt?x=14a03a2a880000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=aae2d21e7dd80684
>> dashboard link: https://syzkaller.appspot.com/bug?extid=60748c96cf5c6df8e581
>> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
>> userspace arch: arm64
>>
>> Unfortunately, I don't have any reproducer for this issue yet.
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/11078f50b80b/disk-bbed346d.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/398e5f1e6c84/vmlinux-bbed346d.xz
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+60748c96cf5c6df8e581@syzkaller.appspotmail.com
>
>+Jiri
>
>It looks like the issue is with the team device. It seems to call
>itself infinitely.
>team_device_event was mentioned in stack overflow bugs in the past:
>https://groups.google.com/g/syzkaller-bugs/search?q=%22team_device_event%22
Hi, do you have dmesg output available by any chance?
Thanks!
next prev parent reply other threads:[~2022-10-12 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 7:48 [syzbot] kernel panic: kernel stack overflow syzbot
2022-10-12 7:53 ` Dmitry Vyukov
2022-10-12 12:19 ` Eric Dumazet
2022-10-12 13:31 ` Taehee Yoo
2022-10-13 15:00 ` Taehee Yoo
2022-10-13 16:04 ` Eric Dumazet
2022-10-21 11:08 ` Taehee Yoo
2023-04-07 7:22 ` wangyufen
2023-04-07 8:17 ` Taehee Yoo
2022-10-12 13:11 ` Jiri Pirko [this message]
2022-10-12 13:54 ` Dmitry Vyukov
2022-10-12 15:08 ` Jiri Pirko
2022-10-12 16:42 ` Eric Dumazet
2022-10-13 7:11 ` Jiri Pirko
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=Y0a88zDFLVeVzBPB@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+60748c96cf5c6df8e581@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;
as well as URLs for NNTP newsgroup(s).