linux-kernel - Re: [tip: x86/boot] x86/boot/compressed: Remove .eh

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]

Message-ID: <20200224172857.GA334627@rani.riverdale.lan>
Date:   Mon, 24 Feb 2020 12:28:57 -0500
From:   Arvind Sankar <nivedita@...m.mit.edu>
To:     Borislav Petkov <bp@...e.de>
Cc:     Arvind Sankar <nivedita@...m.mit.edu>,
        linux-tip-commits@...r.kernel.org,
        Nathan Chancellor <natechancellor@...il.com>,
        x86 <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [tip: x86/boot] x86/boot/compressed: Remove .eh_frame section
 from bzImage

On Mon, Feb 24, 2020 at 06:16:18PM +0100, Borislav Petkov wrote:
> On Mon, Feb 24, 2020 at 11:41:29AM -0500, Arvind Sankar wrote:
> > Hi Boris, apologies for the confusion and unnecessary work I've created,
> > but I think the preference is to merge the 2-patch series I posted
> > yesterday [1] instead of this.
> > 
> > [1] https://lore.kernel.org/lkml/20200223193715.83729-1-nivedita@alum.mit.edu/
> 
> What guarantees this would work and we won't hit some corner case or
> toolchain configuration this hasn't been tested on?
> 
> If that happens, I need to have a state to revert back to, i.e., this
> patch, discarding .eh_frame explicitly.
> 
> So I'll pick up [1] too, but give people a couple of days - a chance to
> complain about. :)
> 
> -- 
> Regards/Gruss,
>     Boris.
> 
> SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

Ok, note that the 2-patch series assumed that it would replace this one,
so it doesn't contain a revert of discarding .eh_frame explicitly for
the compressed kernel.

The first patch of that series at least should be safe enough, it will
stop generating .eh_frame sections in most cases, and shouldn't make any
edge cases worse than before. The second one might be a regression if we
do have some case that still creates them though.