Thread (12 messages) 12 messages, 6 authors, 2026-04-10

Re: bluetooth regression fix likely to miss -rc5

flat view

From: Thorsten Leemhuis <hidden>
Date: 2026-03-20 18:26:26
Also in: linux-bluetooth

On 3/20/26 19:02, Luiz Augusto von Dentz wrote:
On Fri, Mar 20, 2026 at 12:47 PM Thorsten Leemhuis
[off-list ref] wrote:
quoted
On 3/20/26 01:00, patchwork-bot+netdevbpf@kernel.org wrote:
quoted
The quoted bluetooth pull to net afaics came a tiny bit too late for
this week's net PR to mainline. I assume there won't be another this
week, as that would be unusual from a look at the history (and well, if
I'm wrong I'm happy!). That is kind of unfortunate, as those bluetooth
changes contained a fix[1] for a regression that at least three people
reported (and I know of at least one other person that was affected)[2].
A regression that is known for nearly a month now and thus already took
way longer than the "fix within a week, preferably before the next rc."
rule of thumb Linus recently mentioned[3].
Afaik, it was tagged as regression on March 1st afaik, according to
[2];
Well, the first report was 2026-02-22
https://bugzilla.kernel.org/show_bug.cgi?id=221120

I don't blame you for missing that, as it took some time to reach you
due to the know deficits of our bugzilla setup (and looking back I could
and should have forwarded it faster once I had noticed it) -- which is
another reason to change something there, but that is a different topic
(see the recent discussion on the ksummit list).
traces were only provided on March 15th, so yeah it was fixed
within a week once the necessary traces were supplied.
Sure, and I can fully understand that you need traces to fix this and
that not reverting the culprit helps motivating someone to provide them.
But OTOH from Linus statement in [3] it sounds like he would have
preferred to see this fixed faster through a revert.

I guess it's not too much of the problem that it took a bit longer from
the report to a fix. But thx to your efforts (many thx for that) we now
have a fix, so I'd say: let's mainline it quickly to (a) get it tested
and (b) prevent more people from running into this, as then they might
bisect for nothing.

Ciao, Thorsten
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help