linux-kernel - Re: [PATCH 1/2] x86/boot/compressed/64: Remove .bss/.pgtable from bzImage

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 19 Feb 2020 12:57:17 -0500
From:   Arvind Sankar <nivedita@...m.mit.edu>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Arvind Sankar <nivedita@...m.mit.edu>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] x86/boot/compressed/64: Remove .bss/.pgtable from
 bzImage

On Wed, Feb 19, 2020 at 01:09:38PM +0100, Borislav Petkov wrote:
> 
> You keep pinging. Why? Is it a showstopper or what is the urgency here?
> 
> This is shaving off some 100 - 200 KiB from the final bzImage, AFAICT. Or
> is there something more broken this is fixing?
> 

There isn't any particular urgency (at least until fg-kaslr patches try
to make it 64MiB bigger), but it's unclear how long to wait before
sending a reminder -- Documentation/process suggests that comments
should be received in a week or so, pinging after 4 and 6 weeks seemed
reasonable. If x86 has a longer queue, might be worth documenting that
somewhere?