From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Matthew Mitchell <matthew@geodev.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: More about nfsd/lockd hang in 2.4.20+NFS_ALL
Date: 13 Jun 2003 08:48:29 -0700 [thread overview]
Message-ID: <shsd6hikmgi.fsf@charged.uio.no> (raw)
In-Reply-To: <3EE9D5BB.6040600@geodev.com>
>>>>> " " == Matthew Mitchell <matthew@geodev.com> writes:
> The code looks like this:
> if (saddr.sin_addr.s_addr != htonl(INADDR_LOOPBACK)
> || ntohs(saddr.sin_port) >= 1024) {
> printk(KERN_WARNING
> "lockd: rejected NSM callback from
> %08x:%d\n",
> ntohl(rqstp->rq_addr.sin_addr.s_addr),
> ntohs(rqstp->rq_addr.sin_port));
> return rpc_system_err;
> }
> In this case, though, the rq_addr.sin_addr.s_addr is that of
> loopback, as it says in the message (7f000001 => 127.0.0.1).
> It would appear that this is a lock notify that's supposed to
> be called when a client reconnects to a server, but it thinks
> it's being called with some impossible values.
It's just saying that the kernel expects rpc.statd to contact it using
a reserved port when notifying it about a reboot of one of the remote
servers.
Most rpc.statd daemons today run setuid some unprivileged
user. Perhaps this is causing bindresvport() to fail?
Cheers,
Trond
-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-06-13 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 13:46 More about nfsd/lockd hang in 2.4.20+NFS_ALL Matthew Mitchell
2003-06-13 15:48 ` Trond Myklebust [this message]
2003-06-13 16:19 ` Matthew Mitchell
2003-06-13 16:31 ` Trond Myklebust
2003-06-13 16:48 ` Matthew Mitchell
2003-06-13 21:21 ` Trond Myklebust
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=shsd6hikmgi.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=matthew@geodev.com \
--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.