linux-kernel - Re: Linux 6.2-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8ec65f01-89fe-bd6f-a2c2-f4dfc0555cc2@leemhuis.info>
Date:   Sun, 22 Jan 2023 14:49:22 +0100
From:   "Linux kernel regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:     Vlastimil Babka <vbabka@...e.cz>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Greg KH <gregkh@...uxfoundation.org>
Subject: Re: Linux 6.2-rc5

[CCing Vlastimil, akpm, and Greg]

On 22.01.23 01:44, Linus Torvalds wrote:
> Ok, so I thought we were back to normal after the winter holidays at
> rc4. Now, a week later, I think I was mistaken - we have fairly
> sizable rc5, so I suspect there was still pent up testing and fixes
> from people being off. [...]

Huh, a -rc on Saturday evening? That's unusual. But well, in that case I
can wait till tomorrow with my regression report, as it's too late for
the rc anyway. :-D

But nevertheless there is one thing I want to bring up, even if -rc5 is
already out: Vlastimil asked me explicitly to highlight ```Revert
"mm/compaction: fix set skip in fast_find_migrateblock"```[1] in my
weekly report[2], as me would prefer if that patch could head to
mainline and especially stable rather sooner than later. He wrote:

```I consider this serious enough to be fixed in mainline+stable ASAP,
hopefully in rc5, as it does hurt people using 6.1.```

See [3] and [4] for the regression reports.

Andrew merged that patch on the 13th[5]. The fix thus by now spend a few
days in linux-next. But that hasn't been the the case yet when Andrew
sent the latest -mm hotfixes to you on the 16th, that's why it's still
in mm.

It's too late now to get it included in -rc5, but maybe Greg is willing
to pick it up for the next stable cycle if you merge it to mainline
today. But obviously it's your decision if that's worth it. And yes,
ideally I should have asked Andrew to send a extra pull request your
way, but I was busy with other stuff and only saw Vlastimil a few hours
ago. :-/ Sorry.

Ciao, Thorsten

[1] https://lore.kernel.org/all/20230113173345.9692-1-vbabka@suse.cz/
[2]
https://lore.kernel.org/all/f47f69f9-7378-f18c-399b-b277c753532e@suse.cz/
[3] https://bugzilla.suse.com/show_bug.cgi?id=1206848
[4]
[5] https://lore.kernel.org/all/20230114041117.B372AC43392@smtp.kernel.org/