From: Tianyi Chen <hi@tychen.cc>
To: kzak@redhat.com
Cc: util-linux@vger.kernel.org
Subject: [PATCH v2 0/2] libmount: preserve reused loop devices and request direct I/O
Date: Sun, 4 Oct 2026 11:41:27 +0900 [thread overview]
Message-ID: <cover.1791081687.git.hi@tychen.cc> (raw)
Hi Karel,
This revision addresses your review of PR #4646. The reused-device fix
is now separate from the direct-I/O option.
Changes in v2:
- Add a specific diagnostic for direct-I/O mode conflicts.
- Use ul_strtobool() and the test-suite cleanup helpers.
- Document buffered-I/O fallback and how to check the effective mode.
- Add the option comment header and reused-device debug message.
- Remove the AI attribution trailer as requested.
Built mount, umount, losetup and findmnt with Meson. As root in a private
mount namespace, loop-reuse, loop-direct-io, regfile and fstab-loop all
passed. The direct-I/O test also checks boolean aliases and the conflict
diagnostic.
Thanks,
Tianyi
Tianyi Chen (2):
libmount: keep reused loop devices attached on mount failure
libmount: support explicit loop direct I/O requests
libmount/src/hook_loopdev.c | 41 +++++++++++++-
sys-utils/mount.8.adoc | 13 ++++-
tests/expected/mount/loop-direct-io | 6 +++
tests/expected/mount/loop-reuse | 1 +
tests/ts/mount/loop-direct-io | 84 +++++++++++++++++++++++++++++
tests/ts/mount/loop-reuse | 23 ++++++++
6 files changed, 165 insertions(+), 3 deletions(-)
create mode 100644 tests/expected/mount/loop-direct-io
create mode 100644 tests/expected/mount/loop-reuse
create mode 100755 tests/ts/mount/loop-direct-io
create mode 100755 tests/ts/mount/loop-reuse
base-commit: 55e3c4dba6101a47ecaae71c91edbe10c59b8d56
--
2.55.0
next reply other threads:[~2026-10-04 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 2:41 Tianyi Chen [this message]
2026-09-21 7:34 ` [PATCH v2 2/2] libmount: support explicit loop direct I/O requests Tianyi Chen
2026-10-02 12:17 ` [PATCH v2 1/2] libmount: keep reused loop devices attached on mount failure Tianyi Chen
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=cover.1791081687.git.hi@tychen.cc \
--to=hi@tychen.cc \
--cc=kzak@redhat.com \
--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