From: Borislav Petkov <bp@alien8.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] x86, putuser: add ASM_CALL_CONSTRAINT
Date: Sun, 24 Mar 2019 22:32:37 +0100 [thread overview]
Message-ID: <20190324213048.GK23289@zn.tnic> (raw)
In-Reply-To: <20190316210127.GA21830@avx2>
On Sun, Mar 17, 2019 at 12:01:27AM +0300, Alexey Dobriyan wrote:
> Clobber stack pointer given that assembly does CALL.
Clobber?
Comment over ASM_CALL_CONSTRAINT talks about something else.
Also, pls change all your subject prefixes to
"x86/uaccess: ..."
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2019-03-24 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 21:01 [PATCH 1/4] x86, putuser: add ASM_CALL_CONSTRAINT Alexey Dobriyan
2019-03-24 21:32 ` 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=20190324213048.GK23289@zn.tnic \
--to=bp@alien8.de \
--cc=adobriyan@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).