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: <20230516203836.3ccfc734@kernel.org> Date: Tue, 16 May 2023 20:38:36 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Arınç ÜNAL <arinc.unal@...nc9.com> Cc: netdev <netdev@...r.kernel.org>, Daniel Golle <daniel@...rotopia.org> Subject: Re: Net related kernel panic caused by commit in next-20230512..next-20230515 On Tue, 16 May 2023 17:42:44 +0300 Arınç ÜNAL wrote: > I get a kernel panic on next-20230515 and next-20230516. next-20230512 > works fine. The panic log is attached. > > The device boots fine with CONFIG_NET disabled which made me think the > netdev mailing list is the best place to report this. > > Tested on Bananapi BPI-R64 with this defconfig. The filesystem is > Buildroot. The devicetree binary being fed to the bootloader is from > next-20230515. > > https://github.com/arinc9/linux/commit/b4a048428ab6f380b4203598aa62635e21015095 Should be now fixed in net/main, by commit d6352dae0903 ("devlink: Fix crash with CONFIG_NET_NS=n")
Powered by blists - more mailing lists