From: Matthew Wilcox <willy@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
Karel Zak <kzak@redhat.com>
Subject: Re: [PATCH 4/4] listmount: allow listing in reverse order
Date: Wed, 12 Jun 2024 14:54:55 +0100 [thread overview]
Message-ID: <Zmmor8Y1x7opCNU1@casper.infradead.org> (raw)
In-Reply-To: <20240607-vfs-listmount-reverse-v1-4-7877a2bfa5e5@kernel.org>
On Fri, Jun 07, 2024 at 04:55:37PM +0200, Christian Brauner wrote:
> util-linux is about to implement listmount() and statmount() support.
> Karel requested the ability to scan the mount table in backwards order
> because that's what libmount currently does in order to get the latest
> mount first. We currently don't support this in listmount(). Add a new
> LISTMOUNT_RESERVE flag to allow listing mounts in reverse order. For
s/RESERVE/REVERSE/g
> whereas with LISTMOUNT_RESERVE it gives:
next prev parent reply other threads:[~2024-06-12 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 14:55 [PATCH 0/4] fs: allow listmount() with reversed ordering Christian Brauner
2024-06-07 14:55 ` [PATCH 1/4] fs: use semaphore gard in listmount() Christian Brauner
2024-06-07 14:55 ` [PATCH 2/4] path: add cleanup helper Christian Brauner
2024-06-07 14:55 ` [PATCH 3/4] fs: simplify error handling Christian Brauner
2024-06-07 14:55 ` [PATCH 4/4] listmount: allow listing in reverse order Christian Brauner
2024-06-12 13:54 ` Matthew Wilcox [this message]
2024-06-13 11:41 ` Christian Brauner
2024-06-07 16:08 ` [PATCH 0/4] fs: allow listmount() with reversed ordering Mateusz Guzik
2024-06-10 13:16 ` Christian Brauner
2024-06-07 19:03 ` Josef Bacik
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=Zmmor8Y1x7opCNU1@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@kernel.org \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).