From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
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>
Subject: Re: [PATCH v2 0/3] Handle delay slot for extable lookup
Date: Sun, 4 Feb 2024 11:45:13 +0000 [thread overview]
Message-ID: <CAHk-=wjvt75XFUWxPQQJZE0Wdi8HtSLtqQm2L-ZrqH7=2g3ByQ@mail.gmail.com> (raw)
In-Reply-To: <716af17c-136b-4852-86ce-a23bafe34fbb@flygoat.com>
On Sun, 4 Feb 2024 at 11:03, Jiaxun Yang <jiaxun.yang@flygoat.com> wrote:
>
> Well this is the tricky part of my assumption.
> In `exception_epc()` `__isa_exception_epc()` stuff is only called if we
> are in delay slot.
> It is impossible for a invalid instruction_pointer to be considered as
> "in delay slot" by hardware.
Ok, I guess I'm convinced this is all safe. Not great, and not exactly
giving me the warm fuzzies, but not buggy.
Linus
next prev parent reply other threads:[~2024-02-04 11:45 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 [this message]
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
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='CAHk-=wjvt75XFUWxPQQJZE0Wdi8HtSLtqQm2L-ZrqH7=2g3ByQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--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=tsbogend@alpha.franken.de \
--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 NNTP newsgroup(s).