mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Longjun Luo <luolongjuna@gmail.com>
Cc: peterz@infradead.org, mbenes@suse.cz, pmladek@suse.com,
	 joe.lawrence@redhat.com, song@kernel.org, puranjay@kernel.org,
	nathan@kernel.org,  ndesaulniers@google.com, morbo@google.com,
	justinstitt@google.com,  live-patching@vger.kernel.org,
	llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 00/11] objtool/klp: DWARF-based cross-build symbol correlation
Date: Fri, 13 Nov 2026 10:34:01 -0800	[thread overview]
Message-ID: <avdWz3m2YJnlGgnS@jpoimboe> (raw)
In-Reply-To: <CAKL4jwXA4OBVLFGAP4DWw6i9d5bneU=Ur=D58FnrssOt7ygm6A@mail.gmail.com>

On Fri, Nov 13, 2026 at 11:58:31AM +0800, Longjun Luo wrote:
> I understand the concern about readability. Since English is not my
> native language, I drafted the content myself and used AI to help with
> the English writing before reviewing and sending it out. I'll keep the
> information density in mind going forward.
> 
> Just to clarify the background: this design comes from my practical work
> on userspace livepatch, and v1/v2 were meant to present the two
> layers of that design as a whole. While dealing with LTO in practice, I
> ran into many recurring correlation issues, so I tried to abstract and
> model the problem systematically rather than hunting for corner cases,
> and I brought that modeling process into this review.
> 
> As noted in the RFC, this patchset is intended to validate the
> feasibility of the approach. I wanted feedback on the overall design
> before deciding whether to take it further.
> 
> Thanks for taking the time to review and share your thoughts.

Thanks, that makes sense, but for upstreaming I think we will need to
take a more iterative approach, even if it ends up causing some
intermediate patches to be obsoleted by later ones.

-- 
Josh

      reply	other threads:[~2026-11-13 18:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 13:31 Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 01/11] objtool/klp: Fix checksums and copying of wide strings Longjun Luo
2026-11-13  2:42   ` Josh Poimboeuf
2026-11-13  4:32     ` Longjun Luo
2026-11-13 18:27       ` Josh Poimboeuf
2026-11-04 13:31 ` [RFC PATCH v2 02/11] objtool/klp: Hash compound literals by content Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 03/11] objtool/klp: Preserve identifier digits when stripping suffixes Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 04/11] objtool/klp: Read symbol identities from DWARF Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 05/11] objtool/klp: Support reduced and split DWARF Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 06/11] klp-build: Require CONFIG_DEBUG_INFO Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 07/11] objtool/klp: Correlate symbols using DWARF identities Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 08/11] objtool/klp: Include symbol identities in reference checksums Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 09/11] objtool/klp: Extend twins through unchanged function references Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 10/11] objtool/klp: Check unmatched data references Longjun Luo
2026-11-04 13:31 ` [RFC PATCH v2 11/11] objtool/klp: Test symbol identity and state preservation Longjun Luo
2026-11-13  2:35 ` [RFC PATCH v2 00/11] objtool/klp: DWARF-based cross-build symbol correlation Josh Poimboeuf
2026-11-13  3:25   ` Longjun Luo
2026-11-13  3:26 ` Josh Poimboeuf
2026-11-13  3:58   ` Longjun Luo
2026-11-13 18:34     ` Josh Poimboeuf [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=avdWz3m2YJnlGgnS@jpoimboe \
    --to=jpoimboe@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=luolongjuna@gmail.com \
    --cc=mbenes@suse.cz \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=puranjay@kernel.org \
    --cc=song@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

all inboxes | Powered by JetHome®