From: Joe Lawrence <joe.lawrence@redhat.com>
To: Song Liu <song@kernel.org>
Cc: live-patching@vger.kernel.org,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH 4/5] objtool/klp: add -z/--fuzz patch rebasing option
Date: Fri, 30 Jan 2026 15:13:59 -0500 [thread overview]
Message-ID: <aX0RBzV5X1lgQ2ec@redhat.com> (raw)
In-Reply-To: <CAPhsuW59dfVk0hVPFWjgvEifUwviFvnCcMZFGMeZfrw3LJaRZA@mail.gmail.com>
On Fri, Jan 30, 2026 at 11:58:06AM -0800, Song Liu wrote:
> On Fri, Jan 30, 2026 at 10:00 AM Joe Lawrence <joe.lawrence@redhat.com> wrote:
> [...]
> > @@ -807,6 +906,8 @@ build_patch_module() {
> > process_args "$@"
> > do_init
> >
> > +maybe_rebase_patches
> > +
> > if (( SHORT_CIRCUIT <= 1 )); then
>
> I think we should call maybe_rebase_patches within this
> if condition.
>
Hi Song,
Ah yeah I stumbled on this, probably overthinking it:
- we want to validate rebased patches (when requested)
- validate_patches() isn't really required for step 1 (building the
original kernel) but ...
- it's nice to check the patches before going off and building a full
kernel
- the patches are needed in step 2 (building the patched kernel) but ...
- patch validation occurs in step 1
so given the way the short circuiting works, I didn't see a good way to
fold it in there. The user might want to jump right to building the
patched kernel with patch rebasing. Maybe that's not valid thinking if
the rebase occurs in step 1 and they are left behind in klp-tmp/ (so
jumping to step 2 will just use the patches in the scratch dir and not
command line?). It's Friday, maybe I'm missing something obvious? :)
--
Joe
next prev parent reply other threads:[~2026-01-30 20:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 17:59 [PATCH 0/5] objtool/klp-build: small fixups and enhancements Joe Lawrence
2026-01-30 17:59 ` [PATCH 1/5] objtool/klp: limit parent .git directory search Joe Lawrence
2026-01-30 17:59 ` [PATCH 2/5] objtool/klp: handle patches that add new files Joe Lawrence
2026-01-30 20:02 ` Josh Poimboeuf
2026-01-30 17:59 ` [PATCH 3/5] objtool/klp: validate patches with git apply --recount Joe Lawrence
2026-01-30 20:05 ` Josh Poimboeuf
2026-01-30 20:38 ` Joe Lawrence
2026-01-30 22:59 ` Josh Poimboeuf
2026-01-30 23:02 ` Josh Poimboeuf
2026-02-03 16:45 ` Joe Lawrence
2026-02-03 17:53 ` Song Liu
2026-02-03 19:47 ` Josh Poimboeuf
2026-01-30 17:59 ` [PATCH 4/5] objtool/klp: add -z/--fuzz patch rebasing option Joe Lawrence
2026-01-30 19:13 ` Song Liu
2026-01-30 19:58 ` Song Liu
2026-01-30 20:13 ` Joe Lawrence [this message]
2026-01-30 20:46 ` Song Liu
2026-01-30 22:54 ` Josh Poimboeuf
2026-01-30 23:20 ` Song Liu
2026-01-30 23:36 ` Josh Poimboeuf
2026-01-30 20:09 ` Josh Poimboeuf
2026-01-30 20:41 ` Joe Lawrence
2026-01-30 23:31 ` Josh Poimboeuf
2026-01-30 17:59 ` [PATCH 5/5] objtool/klp: provide friendlier error messages Joe Lawrence
2026-01-31 0:37 ` Josh Poimboeuf
2026-01-30 19:18 ` [PATCH 0/5] objtool/klp-build: small fixups and enhancements Song Liu
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=aX0RBzV5X1lgQ2ec@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--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