From: Steve Dickson <steved@redhat.com>
To: Richard Weinberger <richard@nod.at>,
linux-nfs <linux-nfs@vger.kernel.org>
Cc: trond.myklebust@hammerspace.com,
chris chilvers <chris.chilvers@appsbroker.com>
Subject: Re: mountd: Possible bug in next_mnt()
Date: Sat, 11 Mar 2023 11:19:19 -0500 [thread overview]
Message-ID: <655a8ee6-dd94-effd-738a-9ce8db8ebed7@redhat.com> (raw)
In-Reply-To: <1497292229.221220.1678287959937.JavaMail.zimbra@nod.at>
Hello,
My apologies... Eating some PTO...
On 3/8/23 10:05 AM, Richard Weinberger wrote:
> Hi!
>
> next_mnt() finds submounts below a given path p.
> While investigating into an issue in my crossmount patches for nfs-utils I noticed
> that it does not work when fsid=root, rootdir=/some/path/ and then "/" is being exported.
> In this case next_mnt() is asked to find submounts of "/" but returns none.
I'm not clear as what you are saying... "rootdir=/some/path/" is not an
export option.
>
> In my opinion this wrong because every mount is a submount of "/".
>
> The following change fixes the problem on my side but I'm not sure whether
> "/" is a special case in mountd where next_mnt() has to bail out.
>
> diff --git a/support/export/cache.c b/support/export/cache.c
> index 2497d4f48df3..be20cb34adcb 100644
> --- a/support/export/cache.c
> +++ b/support/export/cache.c
> @@ -410,13 +410,13 @@ static char *next_mnt(void **v, char *p)
> *v = f;
> } else
> f = *v;
> - while ((me = getmntent(f)) != NULL && l > 1) {
> + while ((me = getmntent(f)) != NULL && l >= 1) {
> char *mnt_dir = nfsd_path_strip_root(me->mnt_dir);
>
> if (!mnt_dir)
> continue;
>
> - if (strncmp(mnt_dir, p, l) == 0 && mnt_dir[l] == '/')
> + if (strncmp(mnt_dir, p, l) == 0 && (l == 1 || mnt_dir[l] == '/'))
> return mnt_dir;
> }
> endmntent(f);
>
> Comments? :-)
Putting this is the correct patch format including a Signed-off-by
signature... would help.
steved.
>
> Thanks,
> //richard
>
next prev parent reply other threads:[~2023-03-11 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 15:05 mountd: Possible bug in next_mnt() Richard Weinberger
2023-03-11 16:19 ` Steve Dickson [this message]
2023-03-11 16:52 ` Richard Weinberger
2023-03-12 13:31 ` Steve Dickson
2023-03-12 13:36 ` Richard Weinberger
2023-03-12 14:20 ` Steve Dickson
2023-03-12 16:51 ` Richard Weinberger
2023-03-15 22:04 ` Richard Weinberger
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=655a8ee6-dd94-effd-738a-9ce8db8ebed7@redhat.com \
--to=steved@redhat.com \
--cc=chris.chilvers@appsbroker.com \
--cc=linux-nfs@vger.kernel.org \
--cc=richard@nod.at \
--cc=trond.myklebust@hammerspace.com \
/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