From: Steve Dickson <SteveD@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH - nfs-utils] gssd: suppress error message if rpc_pipefs dir disappears.
Date: Thu, 05 Sep 2013 12:02:51 -0400 [thread overview]
Message-ID: <5228AB2B.1000608@RedHat.com> (raw)
In-Reply-To: <20130902145750.357c303a@notabene.brown>
On 02/09/13 00:57, NeilBrown wrote:
> It is possible for a race to cause a name to appear when an rpc_pipefs
> dir is scanned but to no longer be present when we try to open it.
>
> So if the error is ENOENT, don't complain.
>
> This is similar to
>
> commit 5ac9bcfd820f09af4d3f87f1f7346d896f70bc9a
> Author: David Jeffery <djeffery@redhat.com>
> Date: Wed Jan 16 15:21:55 2013 -0500
>
> rpc.idmapd: Ignore open failures in dirscancb()
>
> which addressed a similar issue in idmapd.
>
> Signed-off-by: NeilBrown <neilb@suse.de>
Committed!
steved.
>
> diff --git a/utils/gssd/gssd_proc.c b/utils/gssd/gssd_proc.c
> index b7e2bbb..2d3dbec 100644
> --- a/utils/gssd/gssd_proc.c
> +++ b/utils/gssd/gssd_proc.c
> @@ -467,8 +467,9 @@ process_clnt_dir(char *dir, char *pdir)
> }
> sprintf(clp->dirname, "%s/%s", pdir, dir);
> if ((clp->dir_fd = open(clp->dirname, O_RDONLY)) == -1) {
> - printerr(0, "ERROR: can't open %s: %s\n",
> - clp->dirname, strerror(errno));
> + if (errno != ENOENT)
> + printerr(0, "ERROR: can't open %s: %s\n",
> + clp->dirname, strerror(errno));
> goto fail_destroy_client;
> }
> fcntl(clp->dir_fd, F_SETSIG, DNOTIFY_SIGNAL);
>
prev parent reply other threads:[~2013-09-05 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 4:57 [PATCH - nfs-utils] gssd: suppress error message if rpc_pipefs dir disappears NeilBrown
2013-09-05 16:02 ` Steve Dickson [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=5228AB2B.1000608@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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.