Description of problem:

As a result of the changes for bug 1912106 I have found a couple more regressions, this is one.

This is due to exports offset mount ordering.

Version-Release number of selected component (if applicable):
autofs-5.1.4-68.el8


How reproducible:
Always under certain circumstances.

Steps to Reproduce:
1. Setup an NFS server with out of order exports.

Note: the server name I use below is f28 and it is define
in /etc/hosts with an FQDN of f28.long.domain.name.themaw.net.

mkdir /autofs
mkdir /exports
mkdir /exports/data/tmp
mkdir /exports/data/lib

Create /etc/exports as:
/autofs         *(rw,sync,no_subtree_check)
/exports                *(insecure,rw,sync,no_subtree_check)
/exports/data/tmp       *(insecure,rw,sync,no_subtree_check)
/exports/data/lib       *(insecure,rw,sync,no_subtree_check)

Check order of exports returned:
showmount -e
Export list for f28:
/exports/data/lib *
/exports/data/tmp *
/exports          *
/autofs           *

2. Ensure the /net entry in /etc/auto.master is uncommented:
/net    -hosts

3. Start autofs and trigger mount /net/f28/exports/data/tmp:
ls /net/f28/exports/data/tmp

4. stop autofs and observe that shutdown has not succeeded
   cleanly, as it should in this case.
service stop autofs
cat /proc/mounts|grep \/net
-hosts /net autofs rw,relatime,fd=-1,pgrp=21690,timeout=60,minproto=5,maxproto=5,indirect,pipe_ino=-1 0 0
-hosts /net/f28/exports autofs rw,relatime,fd=6,pgrp=21690,timeout=60,minproto=5,maxproto=5,offset,pipe_ino=130159 0 0

5. Cleanup
umount /net/f28/exports /net

Actual results:
Not all mounts can be umounted at shutdown when they should be in this case.


Expected results:
All mounts not in use at shutdown are umounted cleanly.