From: patchwork-bot+linux-riscv@kernel.org
To: Mukesh Pilaniya <mpilaniy@redhat.com>
Cc: linux-riscv@lists.infradead.org, catalin.marinas@arm.com,
will@kernel.org, mark.rutland@arm.com, chenhuacai@kernel.org,
kernel@xen0n.name, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, akpm@linux-foundation.org,
baoquan.he@linux.dev, rppt@kernel.org, pasha.tatashin@soleen.com,
pratyush@kernel.org, ltao@redhat.com, prudo@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
kexec@lists.infradead.org
Subject: Re: [PATCH] kexec: return -ENOEXEC from image probe functions on mismatch
Date: Sun, 01 Nov 2026 22:15:53 +0000 [thread overview]
Message-ID: <179357135307.2624073.4721839203390727689.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813-mpilaniy-v1-1-777d4d0e30f7@redhat.com>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Mike Rapoport (Microsoft) <rppt@kernel.org>:
On Thu, 13 Aug 2026 12:36:29 +0530 you wrote:
> Several kexec_file_load() image probe functions return -EINVAL when
> they do not recognize the image format. A probe function that rejects
> an image should return -ENOEXEC to indicate that the image is not a
> recognized executable format. -EINVAL implies a problem with the
> syscall parameters, not with image recognition.
>
> kexec_image_probe_default() iterates through registered loaders and
> returns the last probe's error code to the caller. That error
> propagates as the kexec_file_load() return value to userspace.
> Returning -EINVAL from a probe when no loader matches is semantically
> incorrect and misleads userspace about the nature of the failure.
>
> [...]
Here is the summary with links:
- kexec: return -ENOEXEC from image probe functions on mismatch
https://git.kernel.org/riscv/c/2792b4b15f14
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-01 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 7:06 Mukesh Pilaniya
2026-08-13 13:13 ` Philipp Rudo
2026-08-14 7:59 ` Mukesh Pilaniya
2026-08-14 14:13 ` Pratyush Yadav
2026-08-14 17:27 ` Mukesh Pilaniya
2026-08-18 9:44 ` Pratyush Yadav
2026-08-19 5:58 ` Mukesh Pilaniya
2026-08-19 9:10 ` Pratyush Yadav
2026-11-01 22:15 ` patchwork-bot+linux-riscv [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=179357135307.2624073.4721839203390727689.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=baoquan.he@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=ltao@redhat.com \
--cc=mark.rutland@arm.com \
--cc=mpilaniy@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjw@kernel.org \
--cc=pratyush@kernel.org \
--cc=prudo@redhat.com \
--cc=rppt@kernel.org \
--cc=will@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®