From: Greg KH <gregkh@linuxfoundation.org>
To: Raoni Fassina Firmino <raoni@linux.ibm.com>
Cc: stable@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] powerpc/64/signal: Fix regression in __kernel_sigtramp_rt64() semantics
Date: Thu, 11 Feb 2021 13:33:48 +0100 [thread overview]
Message-ID: <YCUkLNoZjlZEkbZF@kroah.com> (raw)
In-Reply-To: <20210211112809.ao77vciijej5kdu7@work-tp>
On Thu, Feb 11, 2021 at 08:28:09AM -0300, Raoni Fassina Firmino wrote:
> On Wed, Feb 10, 2021 at 03:27:05PM +0100, Greg KH wrote:
> > On Tue, Feb 09, 2021 at 12:02:40PM -0300, Raoni Fassina Firmino wrote:
> > > Repeated the same tests as the upstream code on top of v5.10.14 and
> > > v5.9.16, tested on powerpc64 and powerpc64le, with a glibc build and
> > > running the affected glibc's testcase[2], inspected that glibc's
> > > backtrace() now gives the correct result and gdb backtrace also keeps
> > > working as before.
> > >
> > > I believe this should be backported to releases 5.9 and 5.10 as
> > > userspace is affected in this releases. I hope I had tagged this
> > > correctly in the patch.
> >
> > Now added to 5.10.y, 5.9.y is long end-of-life so there is nothing we
> > can do there, sorry.
>
> No problem, I didn't know 5.9.y was already EOL, that is on me.
Hint, in the future www.kernel.org shows you this :)
next prev parent reply other threads:[~2021-02-11 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 15:02 [PATCH] powerpc/64/signal: Fix regression in __kernel_sigtramp_rt64() semantics Raoni Fassina Firmino
2021-02-10 14:27 ` Greg KH
2021-02-11 11:28 ` Raoni Fassina Firmino
2021-02-11 12:33 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-01 20:05 [PATCH] powerpc/64/signal: Fix regression in __kernel_sigtramp_rt64 semantics Raoni Fassina Firmino
2021-02-02 7:41 ` Nicholas Piggin
2021-02-02 11:18 ` Michael Ellerman
2021-02-02 14:30 ` Raoni Fassina Firmino
2021-02-03 11:46 ` Michael Ellerman
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=YCUkLNoZjlZEkbZF@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=raoni@linux.ibm.com \
--cc=stable@vger.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.