From: Petr Vorel <pvorel@suse.cz>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 0/3] tst_device: add support for overlayfs
Date: Fri, 7 Feb 2025 18:15:10 +0100 [thread overview]
Message-ID: <20250207171510.GA1767469@pevik> (raw)
In-Reply-To: <x498qqhel7f.fsf@segfault.usersys.redhat.com>
Hi Jeff,
> Petr Vorel <pvorel@suse.cz> writes:
> > @Jeff: would it be too hard to parse /proc/self/mountinfo (I suppose
> > /proc/self/mounts is not enough)? I'm looking into libmount code E.e.
> Looking more closely, I think /proc/self/mounts will work just fine. I
> was pointed to mountinfo originally and didn't consider mounts. Thanks
> for the suggestion, that will make this much easier!
Great, thank you! Not dragging libmount as a hard dependency for base library
helps us a lot.
Kind regards,
Petr
> Cheers,
> Jeff
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-02-07 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 22:05 [LTP] [PATCH 0/3] tst_device: add support for overlayfs Jeff Moyer
2025-02-03 22:05 ` [LTP] [PATCH 1/3] lib/tst_device.c: factor out btrfs-specific logic from tst_find_backing_dev Jeff Moyer
2025-02-03 22:05 ` [LTP] [PATCH 2/3] lib/tst_device.c: check for BTRFS_SUPER_MAGIC instead of device major of 0 Jeff Moyer
2025-02-03 22:06 ` [LTP] [PATCH 3/3] lib/tst_device.c: add support for overlayfs Jeff Moyer
2025-02-07 11:23 ` Petr Vorel
2025-02-07 11:37 ` [LTP] [PATCH 0/3] tst_device: " Petr Vorel
2025-02-07 12:38 ` Cyril Hrubis
2025-02-07 15:28 ` Jeff Moyer
2025-02-07 15:27 ` Jeff Moyer
2025-02-07 17:08 ` Jeff Moyer
2025-02-07 17:15 ` Petr Vorel [this message]
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=20250207171510.GA1767469@pevik \
--to=pvorel@suse.cz \
--cc=jmoyer@redhat.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.