linux-kernel - Re: [PATCH] x86/purgatory: Switch to the position-independent small code model

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]

Date: Tue, 30 Apr 2024 15:15:47 +0200 (CEST)
From: Michael Matz <matz@...e.de>
To: Jiri Slaby <jirislaby@...nel.org>
cc: Borislav Petkov <bp@...en8.de>, Ard Biesheuvel <ardb+git@...gle.com>, 
    linux-kernel@...r.kernel.org, x86@...nel.org, 
    Ard Biesheuvel <ardb@...nel.org>, Nathan Chancellor <nathan@...nel.org>, 
    Nick Desaulniers <ndesaulniers@...gle.com>, 
    Bill Wendling <morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>, 
    Song Liu <song@...nel.org>, Ricardo Ribalda <ribalda@...nel.org>, 
    Fangrui Song <maskray@...gle.com>, Arthur Eubanks <aeubanks@...gle.com>, 
    stable@...r.kernel.org
Subject: Re: [PATCH] x86/purgatory: Switch to the position-independent small
 code model

Hello,

On Tue, 30 Apr 2024, Jiri Slaby wrote:

> >> Interesting. I thought gcc doesn't have problems here yet and was
> >> talking to Matz on Thu about it and it seems he's forgotten about his
> >> statement too that "you should simply stop using -mcmodel=large.  Noone
> >> should use it." :-)
> > 
> > It may be so ingrained in my brain that I'm not _always_ saying it when
> > talking about the large code model over a beer.  And indeed I know of no
> > particular problems with it vis GCC,
> 
> Of course you do :).

:-P

> That bsc#1211853 I linked earlier. I.e. gcc-13 +
> -fstrict-flex-arrays=3 + -mcmodel=large + some asm() expecting __FILE__ to be
> constant (not true with the large model).

"asm() expecting $whatever" - clearly a user problem, not a GCC problem 
;-)


Ciao,
Michael.