From: Karel Zak <kzak@redhat.com>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.39
Date: Thu, 18 May 2023 12:23:16 +0200 [thread overview]
Message-ID: <20230518102316.f6s6v6xxnicx646r@ws.net.home> (raw)
In-Reply-To: <20230517-mahnmal-setzen-37937c35cf78@brauner>
On Wed, May 17, 2023 at 03:48:54PM +0200, Christian Brauner wrote:
> This is a very exciting release! There's good reason for us to be happy
> imho. This is the first release of util-linux with comprehensive support
> for the new mount api which is very exciting.
We will see how many things in libmount and kernel are not ready ;-)
> A part of that is of course the support for idmapped mounts and the
> ability to recursively change mount properties, i.e., idempotently
> change the mount properties of a whole mount tree.
>
> It's also great to see support for disk sequence numbers via the
> BLKGETDISKSEQ ioctl and the port to util-linux to rely on
BLKGETDISKSEQ is supported in the blockdev command only.
Lennart has also idea to support it in libmount to verify devices
before the filesystem is attached to VFS.
https://github.com/util-linux/util-linux/issues/1786
That's something we can work on in the next release.
> statx(AT_STATX_DONT_SYNC|AT_NO_AUTOMOUNT) to avoid tripping over
> automounts or hung network filesystems as we just recently discussed
> this!
>
> Thanks for working on this and hopefully we can add the missing pieces
> of the new mount api in the coming months!
I would like to make the v2.40 development cycle shorter. The v2.39
cycle was excessively long and large.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2023-05-18 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 11:22 [ANNOUNCE] util-linux v2.39 Karel Zak
2023-05-17 13:48 ` Christian Brauner
2023-05-18 10:23 ` Karel Zak [this message]
2023-05-18 14:00 ` Christian Brauner
2023-05-18 23:31 ` Bruce Dubbs
2023-05-18 23:42 ` Masatake YAMATO
2023-05-19 22:43 ` Masatake YAMATO
2023-05-19 22:56 ` Bruce Dubbs
2023-05-20 23:16 ` Bruce Dubbs
2023-05-21 21:48 ` Masatake YAMATO
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=20230518102316.f6s6v6xxnicx646r@ws.net.home \
--to=kzak@redhat.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=util-linux@vger.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;
as well as URLs for NNTP newsgroup(s).