From: Rui Qi <qirui.001@bytedance.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: bp@alien8.de, mingo@redhat.com, tglx@linutronix.de,
hpa@zytor.com, jpoimboe@redhat.com, peterz@infradead.org,
mbenes@suse.cz, gregkh@linuxfoundation.org,
stable@vger.kernel.org, alexandre.chartre@oracle.com,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH 0/3] Support intra-function call validation
Date: Wed, 28 Feb 2024 10:50:55 +0800 [thread overview]
Message-ID: <72b3f614-aeef-473f-9496-6a5ed81916a4@bytedance.com> (raw)
In-Reply-To: <20240226172843.52zidtcasjw4wbmh@treble>
I tested the mainline kernel v6.8-rc5 without this problem, as I said before, this problem only occurs in 5.4 LTS, to be precise, it can occur from v5.4.217, with CONFIG_RETPOLINE and CONFIG_LIVEPATCH enabled
BTW: The patch for V2 version has been sent out. We can discuss based on that. Thank you!
https://lore.kernel.org/stable/20240228024535.79980-1-qirui.001@bytedance.com/T/#t
On 2/27/24 1:28 AM, Josh Poimboeuf wrote:
> On Mon, Feb 26, 2024 at 07:33:53PM +0800, qirui wrote:
>> This issue only occurs in 5.4 LTS versions after LTS 5.4.250
>> (inclusive), and this patchset is based on commit
>> 6e1f54a4985b63bc1b55a09e5e75a974c5d6719b (Linux 5.4.269)
>
> Does the bug also exist in mainline? If not, why?
>
prev parent reply other threads:[~2024-02-28 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 9:49 [PATCH 0/3] Support intra-function call validation Rui Qi
2024-02-26 9:49 ` [PATCH 1/3] objtool: is_fentry_call() crashes if call has no destination Rui Qi
2024-02-26 13:29 ` Greg KH
2024-02-26 9:49 ` [PATCH 2/3] objtool: Add support for intra-function calls Rui Qi
2024-02-26 9:49 ` [PATCH 3/3] x86/speculation: Support intra-function call validation Rui Qi
2024-02-26 11:33 ` [PATCH 0/3] " qirui
2024-02-26 17:28 ` Josh Poimboeuf
2024-02-28 2:50 ` Rui Qi [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=72b3f614-aeef-473f-9496-6a5ed81916a4@bytedance.com \
--to=qirui.001@bytedance.com \
--cc=alexandre.chartre@oracle.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).