From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ben Hutchings <ben@decadent.org.uk>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, linux-mm@kvack.org,
Xi Ruoyao <xry111@xry111.site>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 0/3] Handle delay slot for extable lookup
Date: Mon, 12 Feb 2024 23:10:50 +0100 [thread overview]
Message-ID: <ZcqXaqCnKuhMDgqt@alpha.franken.de> (raw)
In-Reply-To: <20240202-exception_ip-v2-0-e6894d5ce705@flygoat.com>
On Fri, Feb 02, 2024 at 12:30:25PM +0000, Jiaxun Yang wrote:
> 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.
>
> Thanks!
>
> [1]: https://lore.kernel.org/lkml/75e9fd7b08562ad9b456a5bdaacb7cc220311cc9.camel@xry111.site
>
> To: Oleg Nesterov <oleg@redhat.com>
>
> To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
>
> To: Andrew Morton <akpm@linux-foundation.org>
> To: Ben Hutchings <ben@decadent.org.uk>
>
> Cc: <linux-arch@vger.kernel.org>
> Cc: <linux-kernel@vger.kernel.org>
>
> Cc: <linux-mips@vger.kernel.org>
>
> Cc: <linux-mm@kvack.org>
>
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
> Changes in v2:
> - Reduce diffstat by implemente fallback macro in linux/ptrace.h (linus)
> - Link to v1: https://lore.kernel.org/r/20240201-exception_ip-v1-0-aa26ab3ee0b5@flygoat.com
>
> ---
> Jiaxun Yang (3):
> ptrace: Introduce exception_ip arch hook
> MIPS: Clear Cause.BD in instruction_pointer_set
> mm/memory: Use exception ip to search exception tables
>
> arch/mips/include/asm/ptrace.h | 3 +++
> arch/mips/kernel/ptrace.c | 7 +++++++
> include/linux/ptrace.h | 4 ++++
> mm/memory.c | 4 ++--
> 4 files changed, 16 insertions(+), 2 deletions(-)
series applied to mips-fixes.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2024-02-12 22:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 12:30 [PATCH v2 0/3] Handle delay slot for extable lookup 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
2024-02-08 9:31 ` Jiaxun Yang
2024-02-12 22:10 ` Thomas Bogendoerfer [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=ZcqXaqCnKuhMDgqt@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--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=xry111@xry111.site \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).