linux-kernel - Re: [PATCH 1/7] x86/entry: Fix #UD vs WARN more

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:   Thu, 18 Jun 2020 17:50:17 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Andy Lutomirski <luto@...capital.net>
Cc:     Josh Poimboeuf <jpoimboe@...hat.com>, linux-kernel@...r.kernel.org,
        x86@...nel.org, dvyukov@...gle.com, elver@...gle.com,
        andreyknvl@...gle.com, Mark.Rutland@....com, mhelsley@...are.com,
        rostedt@...dmis.org, jthierry@...hat.com, mbenes@...e.cz
Subject: Re: [PATCH 1/7] x86/entry: Fix #UD vs WARN more

On Thu, Jun 18, 2020 at 07:57:35AM -0700, Andy Lutomirski wrote:
> 
> 
> > On Jun 18, 2020, at 7:50 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> > 
> > vmlinux.o: warning: objtool: exc_invalid_op()+0x47: call to probe_kernel_read() leaves .noinstr.text section
> > 
> > Since we use UD2 as a short-cut for 'CALL __WARN', treat it as such.
> > Have the bare exception handler do the report_bug() thing.
> 
> I think you should consider inlining or noinstr-ifying report_bug()
> too if you want to make this more bulletproof. I admit the scenario
> where someone instruments it and it goes wrong is farfetched.

How far down that rabbit hole do we go? Because then we need to noinstr
printk, the console drivers, those will very quickly pull in lovely bits
like PCI, USB, DRM :/

At some point we have to just give up.