Linux NFS development
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
	trond myklebust <trond.myklebust@hammerspace.com>,
	chris chilvers <chris.chilvers@appsbroker.com>
Subject: Re: mountd: Possible bug in next_mnt()
Date: Wed, 15 Mar 2023 23:04:30 +0100 (CET)	[thread overview]
Message-ID: <1335921550.247985.1678917870352.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <404384146.237438.1678639902506.JavaMail.zimbra@nod.at>

----- Ursprüngliche Mail -----
>> I'm still trying to reproduce problem... I have
>> 
>> /etc/nfs.conf: rootdir=/export
>> 
>> /etc/exports:
>> /home *(rw,sec=sys:krb5:krb5i:krb5p)
>> /tmp *(rw,fsid=666,all_squash)
>> / *(rw,fsid=root,all_squash)
>> 
>> I'm not seeing the problem... Where does the crossmount come in?
> 
> Chris reported the problem to me while he was testing my re-export/crossmount
> patches.
> I can try reproducing without re-exporting later.

Finally I found some cycles to reproduce without my re-exporting setup.

1. /etc/exports contains:
/       *(rw,crossmnt,no_subtree_check,fsid=root)

2. /etc/nfs.conf contains:

[exports]
 rootdir=/nfs_srv
 
3. Mounts:

/root/fs1.ext4 on /nfs_srv type ext4 (rw,relatime)
/root/fs2.ext4 on /nfs_srv/fs2 type ext4 (rw,relatime)

4. On the client:

# ls /nfs_client/fs2
ls: cannot open directory '/nfs_client/fs2': Stale file handle

I'll send a proper patch ASAP.
next_mnt() has to deal with "/" too.

Thanks,
//richard

      reply	other threads:[~2023-03-15 22:04 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
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 [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=1335921550.247985.1678917870352.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=chris.chilvers@appsbroker.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.com \
    --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