From: Greg KH <gregkh@linuxfoundation.org>
To: Rui Qi <qirui.001@bytedance.com>
Cc: bp@alien8.de, mingo@redhat.com, tglx@linutronix.de,
hpa@zytor.com, jpoimboe@redhat.com, peterz@infradead.org,
mbenes@suse.cz, stable@vger.kernel.org,
alexandre.chartre@oracle.com, x86@kernel.org,
linux-kernel@vger.kernel.org, yuanzhu@bytedance.com
Subject: Re: [External] Re: [PATCH v2 0/3] Support intra-function call validation
Date: Tue, 5 Mar 2024 06:13:52 +0000 [thread overview]
Message-ID: <2024030506-observant-clamor-1c8f@gregkh> (raw)
In-Reply-To: <c98aa910-7b14-401d-a257-274682bb7486@bytedance.com>
On Tue, Mar 05, 2024 at 11:28:01AM +0800, Rui Qi wrote:
> Hi Greg,
> I checked out commit e133c1ee6d7271007fdba3dbe78818afd88943f9 (Linux 5.4.270), applied my patche set on top, enabled CONFIG_LIVEPATCH based on x86 defconfig, compiled without any issues. I couldn't even grep unwind_hint_empty in the codebase, so I'm quite puzzled about how this phenomenon occurred. Can you tell me how to reproduce this compilation error?
Try building with 'make allmodconfig'. Also, what compiler and version are you using?
> In addition, my patchset only applies to the LTS branch of 5.4, not to other branches. Please be careful not to merge it into other branches.Other stable branches do not have the problem of such kernel livepatch issue.
It just broke this branch, I didn't apply it anywhere else.
thanks,
greg k-h
next prev parent reply other threads:[~2024-03-05 6:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 2:45 [PATCH v2 0/3] Support intra-function call validation Rui Qi
2024-02-28 2:45 ` [PATCH v2 1/3] objtool: is_fentry_call() crashes if call has no destination Rui Qi
2024-02-28 2:45 ` [PATCH v2 2/3] objtool: Add support for intra-function calls Rui Qi
2024-02-28 2:45 ` [PATCH v2 3/3] x86/speculation: Support intra-function call validation Rui Qi
2024-03-04 10:41 ` [PATCH v2 0/3] " Greg KH
2024-03-04 10:55 ` Greg KH
2024-03-05 3:28 ` [External] " Rui Qi
2024-03-05 6:13 ` Greg KH [this message]
2024-03-05 6:28 ` Rui Qi
2024-03-05 7:20 ` Greg KH
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=2024030506-observant-clamor-1c8f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.chartre@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qirui.001@bytedance.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yuanzhu@bytedance.com \
/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