From: Greg KH <gregkh@linuxfoundation.org>
To: Mathias Stearn <mathias@mongodb.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
stable@vger.kernel.org, catalin.marinas@arm.com,
peterz@infradead.org
Subject: Re: [PATCH 7.0] arm64/entry: Fix arm64-specific rseq brokenness
Date: Fri, 19 Jun 2026 07:39:03 +0200 [thread overview]
Message-ID: <2026061930-tightrope-bronze-4198@gregkh> (raw)
In-Reply-To: <CAHnCjA3HBwt-rtgmyfanu9wA0eNc3oQqHemPOwUVfp9kotuEwg@mail.gmail.com>
On Thu, Jun 18, 2026 at 10:50:00PM +0200, Mathias Stearn wrote:
> On Thu, Jun 18, 2026 at 5:14 PM Mark Rutland <mark.rutland@arm.com> wrote:
> > Mathias Stearn reports that since v6.19, there are two big issues
> > affecting rseq:
> > [...]
> > The other rseq fixes made it into v7.1 and were all backported to v7.0.y
> > as of v7.0.10. We forgot to CC stable, so this patch was missed.
> >
> > This isn't needed for earlier stable trees.
>
> What about 6.19 itself, or is that not a stable tree? AFAIK it isn't a
> priority for us (MongoDB) like 7.0 is, but I felt like mentioning it
> for completeness, since rseq is quite broken on arm64 with 6.19 today.
If you look at the front page of kernel.org, you will note that 6.19 has
gone end-of-life a long time ago, sorry. We aren't supporting that
anymore at all.
thanks,
greg k-h
next prev parent reply other threads:[~2026-06-19 5:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 15:14 [PATCH 7.0] arm64/entry: Fix arm64-specific rseq brokenness Mark Rutland
2026-06-18 20:50 ` Mathias Stearn
2026-06-19 5:39 ` Greg KH [this message]
2026-06-20 11:54 ` Sasha Levin
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=2026061930-tightrope-bronze-4198@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=mark.rutland@arm.com \
--cc=mathias@mongodb.com \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox