From: Sven Eckelmann <sven@narfation.org>
To: "Ömer Mete Kaya" <omermetekaya0@gmail.com>
Cc: marek.lindner@mailbox.org, sw@simonwunderlich.de,
antonio@mandelbit.com, b.a.t.m.a.n@lists.open-mesh.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net,
syzbot+61b202fdc410840f0198@syzkaller.appspotmail.com
Subject: Re: [PATCH batadv-next v3] batman-adv: tt: batch BH re-enable during TT hash walks
Date: Sun, 08 Nov 2026 08:35:01 +0100 [thread overview]
Message-ID: <2056587.PYKUYFuaPT@sven-l14> (raw)
In-Reply-To: <20261108000137.822325-1-omermetekaya0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2199 bytes --]
On Sunday, 8 November 2026 01:01:11 CET Ömer Mete Kaya wrote:
> Each spin_unlock_bh() re-enables bottom halves and, when softirqs are
> pending, processes them inline before returning. During a 1024-bucket
> TT hash walk under network load, the purge worker can be repeatedly
> interrupted by inline softirq processing at every bucket boundary.
[...]
I already told you that this is not directly for net or net-next. Please don't
send this to netdev@vger.kernel.org or davem@davemloft.net. The scripts also
tell you this:
$ ./scripts/get_maintainer.pl ./20261108000137.822325-1-omermetekaya0@gmail.com.mbx
Marek Lindner <marek.lindner@mailbox.org> (maintainer:BATMAN ADVANCED)
Simon Wunderlich <sw@simonwunderlich.de> (maintainer:BATMAN ADVANCED)
Antonio Quartulli <antonio@mandelbit.com> (maintainer:BATMAN ADVANCED)
Sven Eckelmann <sven@narfation.org> (maintainer:BATMAN ADVANCED)
Sebastian Andrzej Siewior <bigeasy@linutronix.de> (maintainer:Real-time Linux (PREEMPT_RT):Keyword:PREEMPT_RT)
Clark Williams <clrkwllms@kernel.org> (maintainer:Real-time Linux (PREEMPT_RT):Keyword:PREEMPT_RT)
Steven Rostedt <rostedt@goodmis.org> (maintainer:Real-time Linux (PREEMPT_RT):Keyword:PREEMPT_RT)
b.a.t.m.a.n@lists.open-mesh.org (moderated list:BATMAN ADVANCED)
linux-kernel@vger.kernel.org (open list)
linux-rt-devel@lists.linux.dev (open list:Real-time Linux (PREEMPT_RT):Keyword:PREEMPT_RT)
Real-time Linux (PREEMPT_RT) status: Supported:Keyword:PREEMPT_RT
And please don't send two versions of the same patch (series) in less than
24h.
> diff --git a/net/batman-adv/translation-table.c b/net/batman-adv/translation-table.c
> index b9407ad..ebeb486 100644
> --- a/net/batman-adv/translation-table.c
> +++ b/net/batman-adv/translation-table.c
> @@ -36,6 +36,7 @@
> #include <linux/overflow.h>
> #include <linux/rculist.h>
> #include <linux/rcupdate.h>
> +#include <linux/sched.h>
> #include <linux/skbuff.h>
> #include <linux/slab.h>
> #include <linux/spinlock.h>
Why do you include linux/sched.h? The correct include would have been
#include <linux/bottom_half.h>
#syz test: https://git.open-mesh.org/batadv.git disable-bh
Regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-11-08 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 0:01 Ömer Mete Kaya
2026-11-08 7:35 ` Sven Eckelmann [this message]
2026-11-08 8:01 ` [syzbot] [arm?] BUG: workqueue lockup in batadv_tt_purge syzbot
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=2056587.PYKUYFuaPT@sven-l14 \
--to=sven@narfation.org \
--cc=antonio@mandelbit.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.lindner@mailbox.org \
--cc=netdev@vger.kernel.org \
--cc=omermetekaya0@gmail.com \
--cc=sw@simonwunderlich.de \
--cc=syzbot+61b202fdc410840f0198@syzkaller.appspotmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®