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>,
Denys Vlasenko <dvlasenk@redhat.com>
Subject: Re: [PATCH v2 0/2] x86/entry: 32-bit facepalm fixes
Date: Sat, 17 Oct 2015 13:43:47 +0200 [thread overview]
Message-ID: <20151017114347.GC3669@pd.tnic> (raw)
In-Reply-To: <cover.1445035014.git.luto@kernel.org>
On Fri, Oct 16, 2015 at 03:42:53PM -0700, Andy Lutomirski wrote:
> Fixes a (correct) warning and an oops. Oddly, both seem to only
> cause problems on some configurations. The second one presumably
> only survived my testing because I didn't test a threaded program.
>
> The first patch is a bit ugly. If that's a problem, suggestions
> are welcome.
>
> Changes from v1: No longer breaks 64-bit builds.
>
> Andy Lutomirski (2):
> x86/entry/32: Fix entry_INT80_32 to expect interrupts to be on
> x86/entry/32: Fix FS and GS restore in opportunistic SYSEXIT
>
> arch/x86/entry/common.c | 15 ++++++++++++---
> arch/x86/entry/entry_32.S | 12 ++++++------
> arch/x86/entry/entry_64_compat.S | 2 +-
> 3 files changed, 19 insertions(+), 10 deletions(-)
Looks good.
Reported-and-tested-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
prev parent reply other threads:[~2015-10-17 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 22:42 [PATCH v2 0/2] x86/entry: 32-bit facepalm fixes Andy Lutomirski
2015-10-16 22:42 ` [PATCH v2 1/2] x86/entry/32: Fix entry_INT80_32 to expect interrupts to be on Andy Lutomirski
2015-10-17 2:54 ` Brian Gerst
2015-10-17 4:05 ` Andy Lutomirski
2015-10-18 10:15 ` [tip:x86/asm] x86/entry/32: Fix entry_INT80_32() " tip-bot for Andy Lutomirski
2015-10-19 4:48 ` Andy Lutomirski
2015-10-16 22:42 ` [PATCH v2 2/2] x86/entry/32: Fix FS and GS restore in opportunistic SYSEXIT Andy Lutomirski
2015-10-18 10:16 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2015-10-17 11:43 ` Borislav Petkov [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=20151017114347.GC3669@pd.tnic \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.