From: Greg KH <gregkh@linuxfoundation.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Dave.Martin@arm.com, pihsun@chromium.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] arm64: compat: Don't pull syscall number from regs in" failed to apply to 4.19-stable tree
Date: Tue, 15 Jan 2019 16:40:15 +0100 [thread overview]
Message-ID: <20190115154015.GB2679@kroah.com> (raw)
In-Reply-To: <20190107182635.GD22911@fuggles.cambridge.arm.com>
On Mon, Jan 07, 2019 at 06:26:35PM +0000, Will Deacon wrote:
> On Mon, Jan 07, 2019 at 10:40:11AM +0100, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.19-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > thanks,
> >
> > greg k-h
> >
> > ------------------ original commit in Linus's tree ------------------
> >
> > From 53290432145a8eb143fe29e06e9c1465d43dc723 Mon Sep 17 00:00:00 2001
> > From: Will Deacon <will.deacon@arm.com>
> > Date: Thu, 3 Jan 2019 18:00:39 +0000
> > Subject: [PATCH] arm64: compat: Don't pull syscall number from regs in
> > arm_compat_syscall
> >
> > The syscall number may have been changed by a tracer, so we should pass
> > the actual number in from the caller instead of pulling it from the
> > saved r7 value directly.
>
> Fixed patch below. I don't think we need to consider kernels prior to 4.19.
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2019-01-15 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 9:40 FAILED: patch "[PATCH] arm64: compat: Don't pull syscall number from regs in" failed to apply to 4.19-stable tree gregkh
2019-01-07 18:26 ` Will Deacon
2019-01-15 15:40 ` Greg KH [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=20190115154015.GB2679@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Dave.Martin@arm.com \
--cc=pihsun@chromium.org \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.com \
/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).