From: Xi Ruoyao <xry111@xry111.site>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Oleg Nesterov <oleg@redhat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Andrew Morton <akpm@linux-foundation.org>,
Ben Hutchings <ben@decadent.org.uk>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, linux-mm@kvack.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 0/3] Handle delay slot for extable lookup
Date: Thu, 08 Feb 2024 17:23:24 +0800 [thread overview]
Message-ID: <7636b9072f2b72f6079a65d456c561716c5d90a3.camel@xry111.site> (raw)
In-Reply-To: <63a1738c-5755-4c2e-a4d4-f5047cdb3660@flygoat.com>
On Thu, 2024-02-08 at 09:20 +0000, Jiaxun Yang wrote:
>
>
> 在 2024/2/2 12:30, Jiaxun Yang 写道:
> > Hi all,
> >
> > This series fixed extable handling for architecture delay slot (MIPS).
> >
> > Please see previous discussions at [1].
> >
> > There are some other places in kernel not handling delay slots properly,
> > such as uprobe and kgdb, I'll sort them later.
>
> A gentle ping :-)
>
> This series fixes a regression, perhaps it should go through fixes tree.
If you have Fixes: {sha} and Cc: stable@vger.kernel.org Greg will pick
it up once it's in Linus tree.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-02-08 9:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 12:30 Jiaxun Yang
2024-02-02 12:30 ` [PATCH v2 1/3] ptrace: Introduce exception_ip arch hook Jiaxun Yang
2024-02-02 12:30 ` [PATCH v2 2/3] MIPS: Clear Cause.BD in instruction_pointer_set Jiaxun Yang
2024-02-02 12:30 ` [PATCH v2 3/3] mm/memory: Use exception ip to search exception tables Jiaxun Yang
2024-02-02 18:39 ` [PATCH v2 0/3] Handle delay slot for extable lookup Linus Torvalds
2024-02-02 21:31 ` Jiaxun Yang
2024-02-03 13:56 ` Jiaxun Yang
2024-02-04 7:41 ` Linus Torvalds
2024-02-04 11:03 ` Jiaxun Yang
2024-02-04 11:45 ` Linus Torvalds
2024-02-08 9:20 ` Jiaxun Yang
2024-02-08 9:23 ` Xi Ruoyao [this message]
2024-02-08 9:31 ` Jiaxun Yang
2024-02-12 22:10 ` Thomas Bogendoerfer
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=7636b9072f2b72f6079a65d456c561716c5d90a3.camel@xry111.site \
--to=xry111@xry111.site \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=tsbogend@alpha.franken.de \
/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