From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, Song Liu <song@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Yafang Shao <laoar.shao@gmail.com>
Subject: Re: [RFC PATCH v2 6/7] livepatch/klp-build: add pre-built object support for advanced OOT workflows
Date: Thu, 27 Aug 2026 14:45:21 -0700 [thread overview]
Message-ID: <apCqiGX1QgrS2neQ@jpoimboe> (raw)
In-Reply-To: <20260826195000.455905-7-joe.lawrence@redhat.com>
On Wed, Aug 26, 2026 at 03:49:59PM -0400, Joe Lawrence wrote:
> +setup_oot() {
> + local files=()
> + local rel
> +
> + mkdir -p "$ORIG_DIR" "$PATCHED_DIR"
> +
> + find "$USER_ORIG_DIR" -type f -name "*.o" -printf '%P\n' | mapfile -t files
> + [[ ${#files[@]} -gt 0 ]] || die "no .o files found in $USER_ORIG_DIR"
> + for rel in "${files[@]}"; do
> + [[ -f "$USER_PATCHED_DIR/$rel" ]] ||
> + die "$rel found in orig dir but missing from patched dir"
> + mkdir -p "$ORIG_DIR/$(dirname "$rel")"
> + mkdir -p "$PATCHED_DIR/$(dirname "$rel")"
> + cp -f "$USER_ORIG_DIR/$rel" "$ORIG_DIR/$rel"
> + cp -f "$USER_PATCHED_DIR/$rel" "$PATCHED_DIR/$rel"
> + done
> +
> + touch "$ORIG_DIR/.complete"
> + touch "$PATCHED_DIR/.complete"
> +}
This is basically reimplementing copy_orig_objects() and copy_patched_objects().
> ################################################################################
>
> process_args "$@"
> do_init
>
> +# User provided OOT original and patched object files can jump straight
> +# to checksum + diff + build steps
> +if [[ -n "$USER_ORIG_DIR" ]]; then
> + status "Setting up OOT objects"
> + setup_oot
> +
> + status "Generating original checksums"
> + generate_checksums "$ORIG_DIR" "$ORIG_CSUM_DIR" "$PATCHED_DIR"
> + status "Generating patched checksums"
> + generate_checksums "$PATCHED_DIR" "$PATCHED_CSUM_DIR"
> +
> + status "Diffing objects"
> + diff_objects
> +
> + status "Building patch module: $OUTFILE"
> + build_patch_module
> +
> + status "SUCCESS"
> + exit 0
> +fi
This is basically reimplementing --short-circuit=3.
Instead of --orig-dir and --patched-dir, I wonder if we could just have
--oot-build-cmd (combined with --oot-dir), so the user can specify
whatever make command is needed?
Then do_init() could have something like SRC_DIR="${OOT_DIR:-$PWD}" so
almost all the code for all the steps gets shared, except for the build
command.
The klp-specific build-isms like KCFLAGS could be exported instead of
added to the cmdline.
And then that would be easier for the user too, they wouldn't have to do
the building/copying of objects, filtering the patch, etc.
--
Josh
next prev parent reply other threads:[~2026-08-27 21:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 19:49 [RFC PATCH v2 0/7] klp-build: OOT module support Joe Lawrence
2026-08-26 19:49 ` [RFC PATCH v2 1/7] objtool/klp: simplify read_exports file handling Joe Lawrence
2026-08-26 23:31 ` Song Liu
2026-08-26 19:49 ` [RFC PATCH v2 2/7] objtool/klp: add --symvers option to klp diff Joe Lawrence
2026-08-26 23:31 ` Song Liu
2026-08-26 19:49 ` [RFC PATCH v2 3/7] objtool/klp: allow special section entry size overrides Joe Lawrence
2026-08-27 19:17 ` Josh Poimboeuf
2026-08-26 19:49 ` [RFC PATCH v2 4/7] objtool: add target architecture to usage Joe Lawrence
2026-08-26 19:57 ` sashiko-bot
2026-08-27 19:23 ` Josh Poimboeuf
2026-08-26 19:49 ` [RFC PATCH v2 5/7] livepatch/klp-build: add basic out-of-tree module support Joe Lawrence
2026-08-26 20:00 ` sashiko-bot
2026-08-27 21:21 ` Josh Poimboeuf
2026-08-26 19:49 ` [RFC PATCH v2 6/7] livepatch/klp-build: add pre-built object support for advanced OOT workflows Joe Lawrence
2026-08-26 20:01 ` sashiko-bot
2026-08-27 21:45 ` Josh Poimboeuf [this message]
2026-08-26 19:50 ` [RFC PATCH v2 7/7] livepatch/klp-build: add validation for user-supplied OOT objects Joe Lawrence
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=apCqiGX1QgrS2neQ@jpoimboe \
--to=jpoimboe@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=laoar.shao@gmail.com \
--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