From: Jakub Kicinski <kuba@kernel.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: netdev <netdev@vger.kernel.org>, Daniel Golle <daniel@makrotopia.org>
Subject: Re: Net related kernel panic caused by commit in next-20230512..next-20230515
Date: Tue, 16 May 2023 20:38:36 -0700 [thread overview]
Message-ID: <20230516203836.3ccfc734@kernel.org> (raw)
In-Reply-To: <58e55189-51b5-83c9-356c-90a20200cd01@arinc9.com>
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")
next prev parent reply other threads:[~2023-05-17 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 14:42 Net related kernel panic caused by commit in next-20230512..next-20230515 Arınç ÜNAL
2023-05-17 3:38 ` Jakub Kicinski [this message]
2023-05-17 9:17 ` Arınç ÜNAL
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=20230516203836.3ccfc734@kernel.org \
--to=kuba@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=daniel@makrotopia.org \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.