linux-kernel - Re: A note on the 5.12-rc1 tag

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20210306125437.GA436274@gmail.com>
Date:   Sat, 6 Mar 2021 13:54:37 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     Pavel Machek <pavel@....cz>, Krzysztof Kozlowski <krzk@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Borislav Petkov <bp@...en8.de>,
        Thomas Gleixner <tglx@...utronix.de>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: A note on the 5.12-rc1 tag

* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> But I also can heartily just recommend that people who already _did_
> start on rc1 to rebase their current - hopefully not extensive - work.

Thanks for the heads-up - we just rebased about 50 commits in -tip to 
avoid this bug: our normal workflow is to jump on -rc1 once it's 
released and integrate pending development work that we normally don't 
apply during the merge window. So our special pattern of pent-up 
merging did bite us a little bit - but nothing particularly serious.

> I know I've ranted about rebasing for years, and it has huge 
> downsides, but the operation does exist because sometimes you just 
> need to fix serious errors. So _mindful_ rebasing, understanding why 
> it shouldn't be a normal thing, but doing it when something 
> exceptional happens - that's not wrong.

Yeah, and in this case not sending scarce-resource testers & bisecters 
into the middle of a file corruption bug is definitely the right thing 
to do.

Maybe -next could double check that none of the maintainer trees have 
an -rc1 base? Your note here was kind of low-key. :-)

And maybe there's some bisection helper annotation or hook-script that 
can be embedded in the kernel Git tree to avoid or at least warn about 
particularly nasty bugs?

Thanks,

	Ingo