All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Hannes Diethelm <hannes.diethelm@gmail.com>
Cc: xenomai@lists.linux.dev
Subject: Re: [EVL] Kernel WARNING: notifier callback netevent_handler already registered
Date: Sat, 25 Apr 2026 20:50:50 +0200	[thread overview]
Message-ID: <87340ij2lx.fsf@xenomai.org> (raw)
In-Reply-To: <8e08bda6-1fed-4a5a-9bb3-74f019b05855@gmail.com> (Hannes Diethelm's message of "Sat, 25 Apr 2026 18:24:14 +0200")

Hannes Diethelm <hannes.diethelm@gmail.com> writes:

> Hello
>
> There is a Kernel WARNING: "notifier callback netevent_handler already registered right after boot". It is repeated 5 times.
>
> Config:
> Debian Trixie with xfce4 Desktop
> libevl: r56
> linux-evl: v6.12.67-evl2-rebase
>
> I traced the issue already trough the following code:
> net/core/net_namespace.c:355
> kernel/evl/net/net.c:35
> kernel/evl/net/ipv4/ipv4.c:41
> kernel/evl/net/ipv4/arp.c:323
>
> However, I lack the knowledge to do a proper fix. One way would be to just check in evl_net_init_arp() if it is already
> registered and don't do it more than once but that doesn't feel right.

It looks like the system is instantiating multiple network namespaces,
for each of which we set up an ARP front cache by calling
evl_net_init_arp(). Bad idea to hook a system-wide handler there as
well. Could you confirm this fix [1] works for you?

Thanks for reporting this.

[1] https://gitlab.com/Xenomai/xenomai4/linux-evl/-/commit/569beef061321c2c00d775b13ad0aec1a1d2a416

-- 
Philippe.

  reply	other threads:[~2026-04-25 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25 16:24 [EVL] Kernel WARNING: notifier callback netevent_handler already registered Hannes Diethelm
2026-04-25 18:50 ` Philippe Gerum [this message]
2026-04-25 21:05   ` Hannes Diethelm
2026-04-26 19:24     ` Philippe Gerum
2026-04-26 21:32       ` Hannes Diethelm
2026-04-27  9:18         ` Florian Bezdeka
2026-05-16  8:48           ` Hannes Diethelm
2026-05-16  9:50             ` Jan Kiszka
2026-05-16 12:53               ` Hannes Diethelm
2026-04-27  7:33 ` Paul

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=87340ij2lx.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=hannes.diethelm@gmail.com \
    --cc=xenomai@lists.linux.dev \
    /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.