From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH 0/3] x86/entry/64: Fixes for syscall rework
Date: Sun, 31 Jan 2016 22:46:26 +0100 [thread overview]
Message-ID: <20160131214626.GF22584@pd.tnic> (raw)
In-Reply-To: <cover.1454261517.git.luto@kernel.org>
On Sun, Jan 31, 2016 at 09:33:25AM -0800, Andy Lutomirski wrote:
> I broke iopl(2) with my syscall rework. Fix it up. While debugging
> it, I found a bug in my IRQ state handling. Fix that, too.
>
> Andy Lutomirski (3):
> x86/entry/64: Fix an IRQ state error on ptregs-using syscalls
> x86/entry/64: Fix fast-path syscall return register state
> x86/syscalls/64: Mark sys_iopl as using ptregs
>
> arch/x86/entry/entry_64.S | 23 ++++++++++++++++-------
> arch/x86/entry/syscalls/syscall_64.tbl | 2 +-
> 2 files changed, 17 insertions(+), 8 deletions(-)
Looks good so far:
Reported-and-tested-by: Borislav Petkov <bp@suse.de>
We better hammer on those a lot more until the next merge window for
more confidence.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-01-31 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 17:33 [PATCH 0/3] x86/entry/64: Fixes for syscall rework Andy Lutomirski
2016-01-31 17:33 ` [PATCH 1/3] x86/entry/64: Fix an IRQ state error on ptregs-using syscalls Andy Lutomirski
2016-02-01 8:03 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2016-01-31 17:33 ` [PATCH 2/3] x86/entry/64: Fix fast-path syscall return register state Andy Lutomirski
2016-02-01 8:03 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2016-01-31 17:33 ` [PATCH 3/3] x86/syscalls/64: Mark sys_iopl as using ptregs Andy Lutomirski
2016-02-01 8:04 ` [tip:x86/asm] x86/syscalls/64: Mark sys_iopl() " tip-bot for Andy Lutomirski
2016-01-31 21:46 ` Borislav Petkov [this message]
2016-02-01 7:58 ` [PATCH 0/3] x86/entry/64: Fixes for syscall rework Ingo Molnar
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=20160131214626.GF22584@pd.tnic \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=x86@kernel.org \
/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