From: Pratyush Yadav <pratyush@kernel.org>
To: Tarun Sahu <tarunsahu@google.com>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
vipinsh@google.com
Subject: Re: [PATCH] liveupdate: Document that retrieve failure is permanent
Date: Tue, 09 Jun 2026 17:54:24 +0200 [thread overview]
Message-ID: <2vxzfr2vso9b.fsf@kernel.org> (raw)
In-Reply-To: <074445fc4964961f12171ea129f2a7690322a78a.1780944056.git.tarunsahu@google.com> (Tarun Sahu's message of "Mon, 8 Jun 2026 18:42:50 +0000")
On Mon, Jun 08 2026, Tarun Sahu wrote:
> Signed-off-by: Tarun Sahu <tarunsahu@google.com>
> ---
> include/uapi/linux/liveupdate.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/liveupdate.h b/include/uapi/linux/liveupdate.h
> index 30bc66ee9436..a564d2bd05c1 100644
> --- a/include/uapi/linux/liveupdate.h
> +++ b/include/uapi/linux/liveupdate.h
> @@ -168,7 +168,8 @@ struct liveupdate_session_preserve_fd {
> * associated with the token and populates the @fd field with a new file
> * descriptor referencing the restored resource in the current (new) kernel.
> * This operation must be performed *before* signaling completion via
> - * %LIVEUPDATE_IOCTL_FINISH.
> + * %LIVEUPDATE_IOCTL_FINISH. Once retrieve call is failed, retrieve status
> + * is saved. So it is permanent failure and retry is pointless.
Perhaps the wording below is slightly better from a user perspective?
If a retrieve of a token fails, subsequent attempts to retrieve the
token fail with the same error code. Failed retrieves are not
retried.
> *
> * Return: 0 on success, negative error code on failure (e.g., invalid token).
> */
>
> base-commit: 2d3090a8aeb596a26935db0955d46c9a5db5c6ce
> prerequisite-patch-id: 30753743cdfab5c3c5355ecde725b6648f1b7a17
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-06-09 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 18:42 [PATCH] liveupdate: Document that retrieve failure is permanent Tarun Sahu
2026-06-09 15:54 ` Pratyush Yadav [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=2vxzfr2vso9b.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=tarunsahu@google.com \
--cc=vipinsh@google.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