[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABV8kRzbGgF4Uc9+VyzBUiH-kGfMALd8tDtjE3hjyE2Z5VD3-g@mail.gmail.com>
Date: Wed, 15 Apr 2020 21:14:50 -0400
From: Keno Fischer <keno@...iacomputing.com>
To: Andy Lutomirski <luto@...nel.org>
Cc: Dave Hansen <dave.hansen@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andi Kleen <andi@...stfloor.org>,
Kyle Huey <khuey@...ehuey.com>,
"Robert O'Callahan" <robert@...llahan.org>
Subject: Re: [RFC PATCH v2] x86/arch_prctl: Add ARCH_SET_XCR0 to set XCR0 per-thread
> Would it make matters easier if tasks with nonstandard XCR0 were not
> allowed to use ptrace() at all? And if ARCH_SET_XCR0 were disallowed
> if the caller is tracing anyone?
That would be fine by me (as long as you're still allowed to ptrace them of
course). I do think that using the kernel XCR0 is the best choice, but since
I don't really have a use case for it, I'm happy to disallow that and
let anybody who does have a use case come back here and
argue for it one way or the other.
Powered by blists - more mailing lists