From: Pasha Tatashin <pasha.tatashin@soleen.com>
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, vipinsh@google.com,
kexec@lists.infradead.org
Subject: Re: [PATCH v2] liveupdate: Document that retrieve failure is permanent
Date: Thu, 11 Jun 2026 18:13:49 +0000 [thread overview]
Message-ID: <air6nKKX0FGs7Bwu@plex> (raw)
In-Reply-To: <faec5df2a3e90240cde5897bae2250cd7d44aeac.1781170056.git.tarunsahu@google.com>
On 06-11 09:30, Tarun Sahu wrote:
Please include at least a sentence in the commit log.
Otherwise,
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> Signed-off-by: Tarun Sahu <tarunsahu@google.com>
> ---
> include/uapi/linux/liveupdate.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/liveupdate.h b/include/uapi/linux/liveupdate.h
> index 30bc66ee9436..d06aa24350b5 100644
> --- a/include/uapi/linux/liveupdate.h
> +++ b/include/uapi/linux/liveupdate.h
> @@ -168,7 +168,9 @@ 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. 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
> --
> 2.54.0.1099.g489fc7bff1-goog
>
prev parent reply other threads:[~2026-06-11 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 9:30 [PATCH v2] liveupdate: Document that retrieve failure is permanent Tarun Sahu
2026-06-11 12:33 ` Pratyush Yadav
2026-06-11 12:49 ` Mike Rapoport
2026-06-11 18:13 ` Pasha Tatashin [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=air6nKKX0FGs7Bwu@plex \
--to=pasha.tatashin@soleen.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pratyush@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.