linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jianhong Yin <jiyin@redhat.com>
To: Steve Dickson <SteveD@RedHat.com>
Cc: linux-nfs@vger.kernel.org, "Jianhong.Yin" <yin-jianhong@163.com>
Subject: Re: [PATCH] nfs-utils mount: recover the lost EBUSY
Date: Tue, 25 Sep 2018 22:21:26 -0400 (EDT)	[thread overview]
Message-ID: <1823792730.16120317.1537928486853.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <a9f8b089-b701-f9cd-5ec0-9afa02997c6f@RedHat.com>


----- 原始邮件 -----
> 发件人: "Steve Dickson" <SteveD@RedHat.com>
> 收件人: jiyin@redhat.com
> 抄送: linux-nfs@vger.kernel.org, "Jianhong.Yin" <yin-jianhong@163.com>
> 发送时间: 星期二, 2018年 9 月 25日 下午 11:40:03
> 主题: Re: [PATCH] nfs-utils mount: recover the lost EBUSY
> 
> 
> 
> On 9/17/18 7:38 AM, jiyin@redhat.com wrote:
> > From: "Jianhong.Yin" <yin-jianhong@163.com>
> > 
> > see: https://bugzilla.redhat.com/show_bug.cgi?id=1629705
> > [nfs-utils] mount -osharecache failure but return 'true'
> > 
> > mount.nfs4 -o context=system_u:object_r:user_home_dir_t:s0,sharecache
> > $serv:$expdir $nfsmp
> > mount.nfs4 -o context=system_u:object_r:xferlog_t:s0,sharecache
> > $serv:$expdir $nfsmp2
> > ^^^ here mount fail, but return true. it confuse user!
> > 
> > Anyway, we should not hide the failure and pretend that it
> > does not exist.
> > 
> > Signed-off-by: Jianhong Yin <yin-jianhong@163.com>
> > ---
> >  utils/mount/stropts.c | 9 ---------
> >  1 file changed, 9 deletions(-)
> > 
> > diff --git a/utils/mount/stropts.c b/utils/mount/stropts.c
> > index 4d2e37e..ca5bc7f 100644
> > --- a/utils/mount/stropts.c
> > +++ b/utils/mount/stropts.c
> > @@ -1078,15 +1078,6 @@ static int nfsmount_fg(struct nfsmount_info *mi)
> >  		if (nfs_try_mount(mi))
> >  			return EX_SUCCESS;
> >  
> > -		if (errno == EBUSY)
> > -			/* The only cause of EBUSY is if exactly the desired
> > -			 * filesystem is already mounted.  That can arguably
> > -			 * be seen as success.  "mount -a" tries to optimise
> > -			 * out this case but sometimes fails.  Help it out
> > -			 * by pretending everything is rosy
> > -			 */
> > -			return EX_SUCCESS;
> > -
> >  		if (nfs_is_permanent_error(errno))
> >  			break;
> >  
> > 
> It code is here because of commit 3904d8102 which argues
> the re-mounting of a filesystem that is already mounted
> is not an error... which I tend to agree with...
Got it.

how about : change in kernel  if (re-mounting && busy)  return TRUE from syscall->mount

> 
> steved.
> 

  reply	other threads:[~2018-09-26  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 11:38 [PATCH] nfs-utils mount: recover the lost EBUSY jiyin
2018-09-25 15:40 ` Steve Dickson
2018-09-26  2:21   ` Jianhong Yin [this message]
2018-09-26 18:09     ` Steve Dickson

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=1823792730.16120317.1537928486853.JavaMail.zimbra@redhat.com \
    --to=jiyin@redhat.com \
    --cc=SteveD@RedHat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=yin-jianhong@163.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;
as well as URLs for NNTP newsgroup(s).