From: Luca Boccassi <luca.boccassi@gmail.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: kexec@lists.infradead.org, linux-mm@kvack.org, graf@amazon.com,
rppt@kernel.org, pratyush@kernel.org, brauner@kernel.org
Subject: Re: [PATCH v2] liveupdate: add LIVEUPDATE_SESSION_GET_NAME ioctl
Date: Fri, 17 Apr 2026 23:09:41 +0100 [thread overview]
Message-ID: <CAMw=ZnQ1EMxobX+=6yC-h2_LQuwhtcRox=0hUaGBkUAmzWiX4A@mail.gmail.com> (raw)
In-Reply-To: <huu6stumzw7ziu7i5qsbpo54hmvd4j4g6fge3acrulhwekw7ez@mjjf6psjty2g>
On Fri, 17 Apr 2026 at 22:48, Pasha Tatashin <pasha.tatashin@soleen.com> wrote:
>
> On 04-17 01:36, luca.boccassi@gmail.com wrote:
> > From: Luca Boccassi <luca.boccassi@gmail.com>
> >
> > Userspace when requesting a session via the ioctl specifies a name and
> > gets a FD, but then there is no ioctl to go back the other way and get
> > the name given a LUO session FD. This is problematic especially when
> > there is a userspace orchestrator that wants to check what FDs it is
> > handling for clients without having to do manual string scraping of
> > procfs, or without procfs at all.
> >
> > Add a ioctl to simply get the name from an FD.
> >
> > Signed-off-by: Luca Boccassi <luca.boccassi@gmail.com>
> > ---
> > This was requested by Lennart and Christian when discussing integration
> > with systemd for LUO management.
> >
> > v2: apply one fix from bot review about cleanup on error path:
> > https://sashiko.dev/#/patchset/20260415184536.1155220-1-luca.boccassi%40gmail.com
> > the other comments are invalid: luo is not a kmod, and the write hooks are not set up
>
> Please split into two patches, and also CC to kernel-linux.
Done in v5. I've also merged this series and the LUO_SESSION_MAGIC
series into a single series, as they modify the same unit test source
file, to avoid merge conflicts.
next prev parent reply other threads:[~2026-04-17 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 0:36 luca.boccassi
2026-04-17 21:48 ` Pasha Tatashin
2026-04-17 22:09 ` Luca Boccassi [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-15 18:46 luca.boccassi
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='CAMw=ZnQ1EMxobX+=6yC-h2_LQuwhtcRox=0hUaGBkUAmzWiX4A@mail.gmail.com' \
--to=luca.boccassi@gmail.com \
--cc=brauner@kernel.org \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@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