All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: a dead lock of 'umount.nfs4 /nfs/scratch -l'
Date: Sat, 14 Jan 2023 01:00:31 +0800	[thread overview]
Message-ID: <20230114010030.D461.409509F4@e16-tech.com> (raw)
In-Reply-To: <5B9215E4-99FF-4C52-901F-8D909DD165BD@oracle.com>

Hi,

> > On Jan 12, 2023, at 4:30 AM, Wang Yugui <wangyugui@e16-tech.com> wrote:
> > 
> > Hi,
> > 
> >> Hi,
> >> 
> >>> Hi,
> >>> 
> >>> We noticed a dead lock of 'umount.nfs4 /nfs/scratch -l'
> >> 
> >> reproducer:
> >> 
> >> mount /dev/sda1 /mnt/test/
> >> mount /dev/sda2 /mnt/scratch/
> >> systemctl restart nfs-server.service
> >> mount.nfs4 127.0.0.1:/mnt/test/ /nfs/test/
> >> mount.nfs4 127.0.0.1:/mnt/scratch/ /nfs/scratch/
> >> systemctl stop nfs-server.service
> >> umount -l /nfs/scratch #OK
> >> umount -l /nfs/test #dead lock
> >> 
> >> Best Regards
> >> Wang Yugui (wangyugui@e16-tech.com)
> >> 2023/01/11
> >> 
> >>> kernel: 6.1.5-rc1
> > 
> > This problem happen on kernel 6.2.0-rc3+(upstream) too.
> 
> Can you clarify:
> 
> - By "deadlock" do you mean the system becomes unresponsive, or that
>   just the mount is stuck?

Just the 'mount -l' is stuck.
'Ctrl +C' can stop the 'mount -l', and then the mount point disapear.

> - Can you reproduce in a non-loopback scenario: a separate client and
>   server?

Yes. It happened on separate nfs client and  server too.

tested kernel version: 5.15.85, 6.1.5, 6.2.0-rc3+(upstream)

Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/01/14


      parent reply	other threads:[~2023-01-13 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  8:59 a dead lock of 'umount.nfs4 /nfs/scratch -l' Wang Yugui
2023-01-11  9:35 ` Wang Yugui
2023-01-12  9:30   ` Wang Yugui
2023-01-13 14:41     ` Chuck Lever III
2023-01-13 15:37       ` Trond Myklebust
2023-01-13 17:06         ` Wang Yugui
2023-01-13 17:29           ` Trond Myklebust
2023-01-13 17:00       ` Wang Yugui [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=20230114010030.D461.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    /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.