From: Sasha Levin <sashal@kernel.org>
To: Sven Eckelmann <sven@narfation.org>
Cc: stable@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH 6.12.y] batman-adv: tt: prevent TVLV entry number overflow
Date: Wed, 3 Jun 2026 15:22:15 -0400 [thread overview]
Message-ID: <aiB-5xvBQhgZA1Iz@laps> (raw)
In-Reply-To: <3408862.oiGErgHkdL@ripper>
On Wed, Jun 03, 2026 at 05:44:05PM +0200, Sven Eckelmann wrote:
>On Wednesday, 3 June 2026 17:13:57 CEST Sasha Levin wrote:
>> > [PATCH 6.12.y] batman-adv: tt: prevent TVLV entry number overflow
>> > commit 99d9958fa10fb684b2a8e2c48a8d704122721420 upstream.
>>
>> Thanks Sven. This one doesn't apply to the stable trees as submitted.
>
>This is odd. It was from here (were it applies):
>https://git.open-mesh.org/batadv.git/log/?h=batadv/lts/6.12
>
>Also tested it now on
>https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/
>branch queue/6.12:
>
>b4 shazam 20260529180300.412724-1-sven@narfation.org
>b4 shazam 20260528205744.636746-1-sven@narfation.org
>b4 shazam 20260529180450.413317-1-sven@narfation.org
>b4 shazam 20260529180618.413634-1-sven@narfation.org # this is the relevant one
>b4 shazam 20260528202135.443823-1-sven@narfation.org
>b4 shazam 20260528192733.76065-1-sven@narfation.org
>b4 shazam 20260528194602.258724-1-sven@narfation.org
>b4 shazam 20260529180804.414401-1-sven@narfation.org
>b4 shazam 20260529180905.414737-1-sven@narfation.org
>b4 shazam 20260529181000.415087-1-sven@narfation.org
>b4 shazam 20260529181042.415322-1-sven@narfation.org
>b4 shazam 20260529181125.415543-1-sven@narfation.org
>
>
>This applied fine for me. Or here the patches I've just applied on queue/6.12
>(in my local branch) with the "b4 shazam" commands:
>
>$ git log --pretty=oneline stable-rc/queue/6.12..queue/6.12
>4569694c4f2a053cd2964cad24af604ae4ec2047 (HEAD -> queue/6.12) batman-adv: bla: avoid NULL-ptr deref for claim via dropped interface
>d32927f478de78eb5224ed73432aa4a41d3bdbfb batman-adv: bla: avoid double decrement of bla.num_requests
>ceab9caf4a4da8ee47e4e238b5f416d49cf170a9 batman-adv: iv: recover OGM scheduling after forward packet error
>8b27c099491f34e3e2050e298852295eff0a4a91 batman-adv: tp_meter: avoid role confusion in tp_list
>46f3587c0deaa3fee91d38ffb517a3b597758cb2 batman-adv: tvlv: reject oversized TVLV packets
>8cb77976278ae5aa212908a7392188f7ff042ba0 batman-adv: tvlv: abort OGM send on tvlv append failure
>ecd5b0eaf6fbcdeec2ad328aeeabd39e9c7b8f24 batman-adv: v: stop OGMv2 on disabled interface
>b2fe2f8b69154de1fb8aff110743966f5ebf2293 batman-adv: tp_meter: directly shut down timer on cleanup
>4420ab1d1ee86b11393a3f561a78edbc220395fa batman-adv: tt: prevent TVLV entry number overflow
>09964daa253a0b7427f01ff3b67f396d24caf928 batman-adv: tt: avoid empty VLAN responses
>7829b033f053aafe66080f20b68b4a60c4f58db7 batman-adv: tt: fix TOCTOU race for reported vlans
>f547e2d9c2a51405f256238558699d40449483bc batman-adv: tt: reject oversized local TVLV buffers
>
>I am guessing that some different ordering was used while trying to apply the
>patches. Just ping me in case I should rebase the patches from my lts branches
>on queue/6.12 (or another stable queue) and submit the missing ones in a
>single patchset. But I should most likely only do this after you published the
>stable-rc for these stable versions - otherwise i would also post patches
>which you already have in your queue.
Yup, looks like an ordering issue. Thanks for clearing it up!
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-03 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 11:57 FAILED: patch "[PATCH] batman-adv: tt: prevent TVLV entry number overflow" failed to apply to 6.12-stable tree gregkh
2026-05-29 18:06 ` [PATCH 6.12.y] batman-adv: tt: prevent TVLV entry number overflow Sven Eckelmann
2026-06-03 15:13 ` Sasha Levin
2026-06-03 15:44 ` Sven Eckelmann
2026-06-03 19:22 ` Sasha Levin [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=aiB-5xvBQhgZA1Iz@laps \
--to=sashal@kernel.org \
--cc=stable@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sven@narfation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox