From: Travis <taskboxtester@gmail.com>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Kees Cook <keescook@chromium.org>, Borislav Petkov <bp@alien8.de>,
X86 ML <x86@kernel.org>, Alexei Starovoitov <ast@plumgrid.com>,
Oleg Nesterov <oleg@redhat.com>, Will Drewry <wad@chromium.org>,
Andy Lutomirski <luto@amacapital.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] x86: entry_64.S: always allocate complete "struct pt_regs"
Date: Thu, 12 Feb 2015 20:59:51 -0600 [thread overview]
Message-ID: <54dd6ab7.e8d8b60a.4b1a.ffffde9c@mx.google.com> (raw)
In-Reply-To: <CAK1hOcOQRfXmimpjaDe=Sr6ZgAMrm7bYh_+Y9QLsU8t=sFHxow@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1098 bytes --]
I'll read this later and get back to you.
On Feb 12, 2015 7:54 PM, Denys Vlasenko <vda.linux@googlemail.com> wrote:
>
> On Thu, Feb 12, 2015 at 11:29 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> >> Thanks!
> >> The renaming of macros caught the bug at compile time, as intended.
> >>
> >> I'll send an updated patch set v3 in a minute. It will have
> >> additional patch in front, since that location in code
> >> also wrongly uses R11 instead of ARGOFFSET.
> >
> > If you aren't already, can you base it here:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=x86/entry
>
> Yes, the most recent 3-patch set is on top of that tree.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
prev parent reply other threads:[~2015-02-13 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 21:55 [PATCH 1/2] x86: entry_64.S: always allocate complete "struct pt_regs" Denys Vlasenko
2015-02-11 21:55 ` [PATCH 2/2] x86: entry_64.S: fix comments. No code changes Denys Vlasenko
2015-02-12 17:17 ` [PATCH 1/2] x86: entry_64.S: always allocate complete "struct pt_regs" Borislav Petkov
2015-02-12 21:53 ` Denys Vlasenko
2015-02-12 22:29 ` Andy Lutomirski
2015-02-13 1:54 ` Denys Vlasenko
2015-02-13 2:59 ` Travis [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=54dd6ab7.e8d8b60a.4b1a.ffffde9c@mx.google.com \
--to=taskboxtester@gmail.com \
--cc=ast@plumgrid.com \
--cc=bp@alien8.de \
--cc=dvlasenk@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.com \
--cc=wad@chromium.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