linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Luca Giuzzi <luca.giuzzi@gmail.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] rpc.idmapd dies with 'I/O possible'
Date: Mon, 16 May 2011 10:39:31 -0400	[thread overview]
Message-ID: <20110516143931.GB31848@fieldses.org> (raw)
In-Reply-To: <4DD13350.1000207@RedHat.com>

On Mon, May 16, 2011 at 10:23:12AM -0400, Steve Dickson wrote:
> 
> 
> On 05/16/2011 09:38 AM, Luca Giuzzi wrote:
> > Dear All,
> >  we have had problems on some of our machines (all Fedora 14), where
> > rpc.idmapd used to die with an `I/O possible' message at (basically)
> > random times. A strace suggested the issue being in nfsopen() where a
> > signal type is reset before notification is disabled; a signal at just
> > the right time might be the cause of the problem; see
> > https://bugzilla.redhat.com/show_bug.cgi?id=684308
> > I am now proposing the (trivial) patch to the list as well.
> > 
> > Best Regards,
> >   luca giuzzi
> > 
> > --- nfs-utils-1.2.3/utils/idmapd/idmapd.c.orig	2011-05-13
> > 16:27:08.000000000 +0200
> > +++ nfs-utils-1.2.3/utils/idmapd/idmapd.c	2011-05-13 16:27:16.000000000 +0200
> > @@ -778,8 +778,8 @@ nfsopen(struct idmap_client *ic)
> >  	} else {
> >  		event_set(&ic->ic_event, ic->ic_fd, EV_READ, nfscb, ic);
> >  		event_add(&ic->ic_event, NULL);
> > -		fcntl(ic->ic_dirfd, F_SETSIG, 0);
> >  		fcntl(ic->ic_dirfd, F_NOTIFY, 0);
> > +		fcntl(ic->ic_dirfd, F_SETSIG, 0);
> >  		if (verbose > 0)
> >  			xlog_warn("Opened %s", ic->ic_path);
> >  	}
> I just updated the bz with these questions, but we can have the 
> conversation here...
> 
> I'm just a bit concerned by the fact that there are
> a couple of places that sets F_SETSIG and then sets F_NOTIFY, 
> so does that mean those places are potential race cases as 
> well?

I wondered about that too; looking:

utils/gssd/gssd_main_loop.c:		fcntl(tdi->fd, F_NOTIFY,
		      	DN_CREATE|DN_DELETE|DN_MODIFY|DN_MULTISHOT);

utils/gssd/gssd_proc.c:	fcntl(clp->dir_fd, F_NOTIFY, DN_CREATE | DN_DELETE | DN_MULTISHOT);
utils/idmapd/idmapd.c:		if (fcntl(fd, F_NOTIFY,
			DN_CREATE | DN_DELETE | DN_MODIFY | DN_MULTISHOT) == -1) {
utils/idmapd/idmapd.c:			fcntl(ic->ic_dirfd, F_NOTIFY,
			DN_CREATE | DN_DELETE | DN_MULTISHOT);
utils/idmapd/idmapd.c:		fcntl(ic->ic_dirfd, F_NOTIFY, 0);

So the last is the only one where we're turning notifications *off*.

So I think the patch is OK.

--b.

> 
> Also, after you applied this patch, did the problem go away?
> Finally, how often did this problem occur?
> 
> tia,
> 
> steved.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-05-16 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 13:38 [PATCH] rpc.idmapd dies with 'I/O possible' Luca Giuzzi
2011-05-16 13:56 ` Jeff Layton
2011-05-16 14:23 ` Steve Dickson
2011-05-16 14:39   ` J. Bruce Fields [this message]
2011-05-16 14:47   ` Luca Giuzzi

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=20110516143931.GB31848@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=luca.giuzzi@gmail.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).