From: Thomas Gleixner <tglx@linutronix.de>
To: Sebastian Mayr <me@sam.st>
Cc: Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uprobes/x86: fix detection of 32-bit user mode
Date: Mon, 19 Aug 2019 20:43:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908192042190.1796@nanos.tec.linutronix.de> (raw)
In-Reply-To: <2d8f1744136431b5eb0bda24ea767374d6fde4e5.camel@sam.st>
On Mon, 19 Aug 2019, Sebastian Mayr wrote:
> > @@ -1056,7 +1056,7 @@ bool arch_uprobe_skip_sstep(struct arch_uprobe
> > *auprobe, struct pt_regs *regs)
> > unsigned long
> > arch_uretprobe_hijack_return_addr(unsigned long trampoline_vaddr,
> > struct pt_regs *regs)
> > {
> > - int rasize = sizeof_long(), nleft;
> > + int rasize = sizeof_long(regs), nleft;
> > unsigned long orig_ret_vaddr = 0; /* clear high bits for 32-bit
> > apps */
> >
> > if (copy_from_user(&orig_ret_vaddr, (void __user *)regs->sp,
> > rasize))
>
> Any feedback on this patch would be greatly appreciated.
Sorry, fell through the cracks. Thanks for the reminder!
next prev parent reply other threads:[~2019-08-19 18:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 15:26 Sebastian Mayr
2019-08-19 18:40 ` Sebastian Mayr
2019-08-19 18:43 ` Thomas Gleixner [this message]
2019-08-23 23:30 ` Thomas Gleixner
2019-08-23 23:44 ` Thomas Gleixner
2019-08-23 23:57 ` Andy Lutomirski
2019-08-24 0:00 ` Thomas Gleixner
2019-08-24 0:03 ` Thomas Gleixner
2019-08-24 0:13 ` Andy Lutomirski
2019-08-24 0:20 ` Thomas Gleixner
2019-08-26 13:48 ` Thomas Gleixner
2019-08-27 14:00 ` get_unmapped_area && in_ia32_syscall (Was: [PATCH] uprobes/x86: fix detection of 32-bit user mode) Oleg Nesterov
2019-08-27 17:03 ` Dmitry Safonov
2019-08-27 23:40 ` Dmitry Safonov
2019-08-28 11:37 ` Oleg Nesterov
2019-08-26 14:02 ` [tip: x86/urgent] uprobes/x86: Fix detection of 32-bit user mode tip-bot2 for Sebastian Mayr
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=alpine.DEB.2.21.1908192042190.1796@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@sam.st \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®