From: Eric Biggers <ebiggers3@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Dmitry Vyukov <dvyukov@google.com>,
Fenghua Yu <fenghua.yu@intel.com>, Kevin Hao <haokexin@gmail.com>,
Oleg Nesterov <oleg@redhat.com>,
Wanpeng Li <wanpeng.li@hotmail.com>,
Yu-cheng Yu <yu-cheng.yu@intel.com>,
Michael Halcrow <mhalcrow@google.com>,
Eric Biggers <ebiggers@google.com>
Subject: [kernel-hardening] Re: [PATCH] x86/fpu: Simplify fpu__activate_fpstate_read()
Date: Sat, 23 Sep 2017 11:28:33 -0700 [thread overview]
Message-ID: <20170923182833.GA542@zzz.localdomain> (raw)
In-Reply-To: <20170923112932.yd7tmoh5kyyazv2t@gmail.com>
On Sat, Sep 23, 2017 at 01:29:32PM +0200, Ingo Molnar wrote:
> > > >
> > > > Ok - could you please rebase these to to tip:master that is at:
> > > >
> > > > git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> > > >
> > > > In particular this has a WIP.x86/fpu branch with FPU fixes+changes queued up but
> > > > not merged upstream (yet), which conflict with these changes. I'd like to merge
> > > > them all together.
> > > >
> > >
> > > Working on it, but there is a problem with current tip. PTRACE_GETREGSET is
> > > causing the following warning:
> >
> > Yes, the warning should be harmless, and I fixed it locally earlier today - does
> > the patch below solve it for you as well?
>
> Note that this fix is now part of tip:master as well, so if you re-test -tip you
> should get all the latest fixes as well (including yours!).
>
No issues so far with the latest tip/master (commit e7c6e3675331).
Eric
prev parent reply other threads:[~2017-09-23 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 18:52 [kernel-hardening] [PATCH v3 0/3] x86/fpu: prevent leaking FPU registers via invalid FPU state Eric Biggers
2017-09-21 18:52 ` [kernel-hardening] [PATCH v3 1/3] x86/fpu: don't let userspace set bogus xcomp_bv Eric Biggers
2017-09-21 19:59 ` Rik van Riel
2017-09-21 18:52 ` [kernel-hardening] [PATCH v3 2/3] x86/fpu: tighten validation of user-supplied xstate_header Eric Biggers
2017-09-21 20:21 ` Rik van Riel
2017-09-21 18:52 ` [kernel-hardening] [PATCH v3 3/3] x86/fpu: reinitialize FPU registers if restoring FPU state fails Eric Biggers
2017-09-21 20:41 ` Rik van Riel
2017-09-22 5:33 ` [kernel-hardening] Re: [PATCH v3 0/3] x86/fpu: prevent leaking FPU registers via invalid FPU state Ingo Molnar
2017-09-22 17:07 ` Eric Biggers
2017-09-23 10:17 ` [kernel-hardening] [PATCH] x86/fpu: Simplify fpu__activate_fpstate_read() Ingo Molnar
2017-09-23 11:29 ` [kernel-hardening] " Ingo Molnar
2017-09-23 18:28 ` Eric Biggers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170923182833.GA542@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=ebiggers@google.com \
--cc=fenghua.yu@intel.com \
--cc=haokexin@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mhalcrow@google.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=wanpeng.li@hotmail.com \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).