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: <Y7RA3bmko0AjO8hQ@zx2c4.com>
Date:   Tue, 3 Jan 2023 15:51:09 +0100
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     linux-kernel@...r.kernel.org, patches@...ts.linux.dev,
        tglx@...utronix.de, linux-crypto@...r.kernel.org,
        linux-api@...r.kernel.org, x86@...nel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>,
        Carlos O'Donell <carlos@...hat.com>,
        Florian Weimer <fweimer@...hat.com>,
        Arnd Bergmann <arnd@...db.de>, Jann Horn <jannh@...gle.com>,
        Christian Brauner <brauner@...nel.org>
Subject: Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type
 from MMIO trace

On Tue, Jan 03, 2023 at 11:32:14AM +0100, Ingo Molnar wrote:
> 
> * Jason A. Donenfeld <Jason@...c4.com> wrote:
> 
> > Both mmiotrace.h and insn-eval.h define various MMIO_ enum constants.
> > Rename the insn ones to have a INSN_ prefix, so that the headers can be
> > used from the same source file.
> > 
> > Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>
> > ---
> >  arch/x86/coco/tdx/tdx.c          | 26 +++++++++++++-------------
> >  arch/x86/include/asm/insn-eval.h | 18 +++++++++---------
> >  arch/x86/kernel/sev.c            | 18 +++++++++---------
> >  arch/x86/lib/insn-eval.c         | 20 ++++++++++----------
> >  4 files changed, 41 insertions(+), 41 deletions(-)
> 
> FYI, I've applied this fix to tip:x86/asm, as the fix for the namespace 
> clash makes sense independently of the vDSO getrandom feature.

I guess you missed the conversation with Borislav yesterday about that.
He mentioned that I'd just take it through random.git when this whole
series goes in.

(Unless of course you wanted to put this into 6.2? That'd be easiest for
me.)

Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ