[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+Z4CCBqyNJCNySYEWUFT-GOfEjYguBfUh_nb6aAe1w99Q@mail.gmail.com>
Date: Wed, 12 Oct 2022 15:54:59 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: syzbot <syzbot+60748c96cf5c6df8e581@...kaller.appspotmail.com>,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
pabeni@...hat.com, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] kernel panic: kernel stack overflow
On Wed, 12 Oct 2022 at 15:11, Jiri Pirko <jiri@...nulli.us> wrote:
>
> Wed, Oct 12, 2022 at 09:53:27AM CEST, dvyukov@...gle.com wrote:
> >On Wed, 12 Oct 2022 at 09:48, syzbot
> ><syzbot+60748c96cf5c6df8e581@...kaller.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@...kaller.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?
Hi Jiri,
syzbot attaches dmesg output to every report under the "console output" link.
Powered by blists - more mailing lists