lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <Y0a88zDFLVeVzBPB@nanopsycho> Date: Wed, 12 Oct 2022 15:11:15 +0200 From: Jiri Pirko <jiri@...nulli.us> To: Dmitry Vyukov <dvyukov@...gle.com> 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 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? Thanks!
Powered by blists - more mailing lists