Re: [PATCH v3 00/12] man2: document "new" mount API
Aleksa Sarai <cyphar-gVpy/LI/[email protected]> Thu, 21 Aug 2025 21:49:18 +1000
| Newsgroups | gmane.linux.kernel.api,gmane.linux.file-systems,gmane.linux.kernel,gmane.linux.man,gmane.linux.kernel.autofs |
|---|---|
| Message-ID | <2025-08-21.1755776865-swank-rusted-doorbell-brads-U3HJFf@cyphar.com> |
On 2025-08-20, Askar Safin <safinaskar-yBVup5oSL51Wk0Htik3J/[email protected]> wrote: > ---- On Sun, 17 Aug 2025 20:16:04 +0400 Aleksa Sarai <cyphar-gVpy/LI/[email protected]> wrote --- > > They are not tested by fstests AFAICS, but that's more of a flaw in > > fstests (automount requires you to have a running autofs daemon, which > > probably makes testing it in fstests or selftests impractical) not the > > feature itself. > > I suggest testing automounts in fstests/selftests using "tracing" automount. > This is what I do in my reproducers. > > > The automount behaviour of tracefs is different to the general automount > > mechanism which is managed by userspace with the autofs daemon. > > Yes. But I still was able to write reproducers using "tracing", so this > automount point is totally okay for tests. (At least for some tests, > such as RESOLVE_NO_XDEV.) Sure, but I don't think people use allyesconfig when running selftests. I wonder if the automated test runners even enable deprecated features like that. In any case, you can definitely write some tests for it. :D -- Aleksa Sarai Senior Software Engineer (Containers) SUSE Linux GmbH https://www.cyphar.com/
signature.asc
(application/pgp-signature, 265 B)
-----BEGIN PGP SIGNATURE----- iJEEABYKADkWIQS2TklVsp+j1GPyqQYol/rSt+lEbwUCaKcHvRsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMSwyLDIACgkQKJf60rfpRG+GeAEAwCxqWJ6XP3XwGopXed+M svbRnf0/cL/a4UUPHvcBzH0BAPDSaOqMP2tkb8R201zdSZfnOP0PAD9/nnceTG96 QpgL =xu3t -----END PGP SIGNATURE-----