From: Garrick Staples <garrick@usc.edu>
To: nfs@lists.sourceforge.net
Subject: Re: mountd segfault on itanium2
Date: Mon, 3 May 2004 11:24:01 -0700 [thread overview]
Message-ID: <20040503182401.GP23287@polop.usc.edu> (raw)
In-Reply-To: <20040501030730.GE23287@polop.usc.edu>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
On Fri, Apr 30, 2004 at 08:07:30PM -0700, Garrick Staples alleged:
> On Fri, Apr 30, 2004 at 04:43:27PM -0700, Garrick Staples alleged:
> > I just spotted a pattern. After collecting several strace samples, it always
> > segfaults after read() or write() to fd 5. And fd 5 is always:
> >
> > open("/proc/net/rpc/nfsd.fh/channel", O_RDWR) = 5
I was able to insert some printf()'s after the write() to fd 5, which means it
is segfaulting after that file.
The segfault is inside svc_getreqset() in utils/mountd/svc_run.c:
switch (selret) {
case -1:
if (errno == EINTR || errno == ECONNREFUSED
|| errno == ENETUNREACH || errno == EHOSTUNREACH)
continue;
xlog(L_ERROR, "my_svc_run() - select: %m");
return;
default:
selret -= cache_process_req(&readfds);
if (selret)
svc_getreqset(&readfds);
}
Either glibc has a bug or the kernel is doing something fugly to the readfds?
--
Garrick Staples, Linux/HPCC Administrator
University of Southern California
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-03 18:28 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 [this message]
2004-05-03 20:47 ` Garrick Staples
2004-05-04 0:17 ` Garrick Staples
2004-05-04 1:01 ` J. Bruce Fields
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=20040503182401.GP23287@polop.usc.edu \
--to=garrick@usc.edu \
--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.