All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: nfs@lists.sourceforge.net
Subject: Re: mountd segfault on itanium2
Date: Mon, 3 May 2004 21:01:58 -0400	[thread overview]
Message-ID: <20040504010158.GD3636@fieldses.org> (raw)
In-Reply-To: <20040504001718.GZ23287@polop.usc.edu>

On Mon, May 03, 2004 at 05:17:18PM -0700, Garrick Staples wrote:
> I'm slowly starting to wrap my brain around how these RPC calls work.  I've
> found something that I can't make sense of.  In my_svc_run(), it packs fds 3,
> 4, 5, 6, and 7 into select().  3, 4, and 5 are 3 files in /proc/net/rpc.  fd 6
>  and 7 are udp and tcp sockets.  During my umount/mount tests, fd 6 is the
> only set bit after the select(), and is then passed to svc_getreqset().
> 
> But just before the segfault, select() sets fd 5, which is
> /proc/net/rpc/nfsd.fh/channel.  The thing that I don't understand is that fd 5
> is being passed to svc_getreqset().  Shouldn't svc_getreqset() be only for fds
> of sockets that have pending rpc calls?  Should fd 5 be cleared from the fdset
> before calling svc_getreqset()?

Cool, good detective work, I think that must be it.  Other people
weren't seeing it because you have to be using the new interface (have
nfsd mounted), and have to get an rpc call and a kernel upcall at the
same time.  Does clearing the bit end the segfaults?

--Bruce Fields

>From Garrick Staples <garrick@usc.edu>:

After mountd handles a cache upcall, we should clear the relevant bits in the
fd_set.


 utils/mountd/cache.c |    1 +
 1 files changed, 1 insertion(+)

diff -puN utils/mountd/svc_run.c~cache_select_bugfix utils/mountd/svc_run.c
diff -puN utils/mountd/cache.c~cache_select_bugfix utils/mountd/cache.c
--- nfs-utils-1.0.6/utils/mountd/cache.c~cache_select_bugfix	2004-05-03 20:57:15.000000000 -0400
+++ nfs-utils-1.0.6-bfields/utils/mountd/cache.c	2004-05-03 20:57:15.000000000 -0400
@@ -315,6 +315,7 @@ int cache_process_req(fd_set *readfds) 
 		    FD_ISSET(fileno(cachelist[i].f), readfds)) {
 			cnt++;
 			cachelist[i].cache_handle(cachelist[i].f);
+			FD_CLR(fileno(cachelist[i].f), readfds);
 		}
 	}
 	return cnt;

_


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-05-04  1:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30 21:24 mountd segfault on itanium2 Garrick Staples
2004-04-30 23:43 ` Garrick Staples
2004-05-01  0:15   ` J. Bruce Fields
2004-05-01  0:24     ` Garrick Staples
2004-05-01  3:07   ` Garrick Staples
2004-05-03 13:35     ` Jose R. Santos
2004-05-03 18:18       ` Garrick Staples
2004-05-03 18:24     ` Garrick Staples
2004-05-03 20:47     ` Garrick Staples
2004-05-04  0:17     ` Garrick Staples
2004-05-04  1:01       ` J. Bruce Fields [this message]
2004-05-04  1:52         ` Garrick Staples
2004-05-04  1:38       ` Garrick Staples

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=20040504010158.GD3636@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=nfs@lists.sourceforge.net \
    /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.