From: Miklos Szeredi <miklos@szeredi.hu>
To: Karel Zak <kzak@redhat.com>
Cc: libc-alpha@sourceware.org, linux-man <linux-man@vger.kernel.org>,
Alejandro Colomar <alx@kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Florian Weimer <fweimer@redhat.com>,
linux-fsdevel@vger.kernel.org, Ian Kent <raven@themaw.net>,
David Howells <dhowells@redhat.com>,
Christian Brauner <christian@brauner.io>,
Amir Goldstein <amir73il@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [RFC] proposed libc interface and man page for listmount
Date: Wed, 6 Dec 2023 10:40:46 +0100 [thread overview]
Message-ID: <CAJfpegtv0A8b2Ex7O0AUwZCFsB_OfXvD_ehYR0a6jMr0F_Okdw@mail.gmail.com> (raw)
In-Reply-To: <20231205182629.qk5s6f7m7sas4anh@ws.net.home>
On Tue, 5 Dec 2023 at 19:26, Karel Zak <kzak@redhat.com> wrote:
>
> On Tue, Dec 05, 2023 at 05:27:58PM +0100, Miklos Szeredi wrote:
> > Attaching the proposed man page for listing mounts (based on the new
> > listmount() syscall).
> >
> > The raw interface is:
> >
> > syscall(__NR_listmount, const struct mnt_id_req __user *, req,
> > u64 __user *, buf, size_t, bufsize, unsigned int, flags);
> >
> > The proposed libc API is.
> >
> > struct listmount *listmount_start(uint64_t mnt_id, unsigned int flags);
> > uint64_t listmount_next(struct listmount *lm);
> > void listmount_end(struct listmount *lm);
>
> What about:
>
> getmountlist()
> nextmountlist()
> freemountlist()
>
> For me, _start and _end() sounds strange. For example, We already use
> get+free for getaddrinfo().
Fine by me. Just wanted to get the general scheme out for comment.
Thanks,
Miklos
next prev parent reply other threads:[~2023-12-06 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 16:27 [RFC] proposed libc interface and man page for listmount Miklos Szeredi
2023-12-05 17:51 ` Matthew House
2023-12-06 9:38 ` Miklos Szeredi
2023-12-06 16:53 ` Matthew House
2023-12-05 18:26 ` Karel Zak
2023-12-06 9:40 ` Miklos Szeredi [this message]
2023-12-06 11:05 ` Florian Weimer
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=CAJfpegtv0A8b2Ex7O0AUwZCFsB_OfXvD_ehYR0a6jMr0F_Okdw@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=alx@kernel.org \
--cc=amir73il@gmail.com \
--cc=arnd@arndb.de \
--cc=christian@brauner.io \
--cc=dhowells@redhat.com \
--cc=fweimer@redhat.com \
--cc=kzak@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=raven@themaw.net \
/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;
as well as URLs for NNTP newsgroup(s).