From: Sven Eckelmann <sven@narfation.org>
To: "Ömer Mete Kaya" <omermetekaya0@gmail.com>,
syzbot+61b202fdc410840f0198@syzkaller.appspotmail.com
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH batadv-next v2] batman-adv: tt: batch BH re-enable during TT hash walks
Date: Sat, 07 Nov 2026 17:09:04 +0100 [thread overview]
Message-ID: <5115119.GXAFRqVoOG@sven-l14> (raw)
In-Reply-To: <20261107153923.797338-1-omermetekaya0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
On Saturday, 7 November 2026 16:37:25 CET Ömer Mete Kaya wrote:
> Closes: https://syzkaller.appspot.com/bug\?extid\=61b202fdc410840f0198
This link doesn't seem to work.
On Saturday, 7 November 2026 16:37:25 CET Ömer Mete Kaya wrote:
> unsigned short vid;
> + u32 buckets_done = 0;
Breaks the reverse x-mas tree order of variable declarations.
(there are multiple occurrences of this problem)
> batadv_tt_global_del_orig():
> Called from workqueue context; yields every 64 buckets. The
> local_bh_enable() is placed before clear_bit() so that pending
> softirqs run while no per-bucket lock is held.
>
Are you sure? It is called from so many different places. Including this one
(which clearly doesn't allow you to sleep due to the spinlock around the
call):
void batadv_purge_orig_ref(struct batadv_priv *bat_priv)
{
[...]
/* for all origins... */
for (i = 0; i < hash->size; i++) {
head = &hash->table[i];
if (hlist_empty(head))
continue;
list_lock = &hash->list_locks[i];
spin_lock_bh(list_lock);
[....]
batadv_tt_global_del_orig(orig_node->bat_priv,
orig_node, -1,
"originator timed out");
[...]
spin_unlock_bh(list_lock);
}
batadv_gw_election(bat_priv);
}
Regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-11-07 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 15:37 [PATCH batadv-next v2] batman-adv: tt: batch BH re-enable during TT hash walks Ömer Mete Kaya
2026-11-07 16:09 ` Sven Eckelmann [this message]
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=5115119.GXAFRqVoOG@sven-l14 \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=omermetekaya0@gmail.com \
--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