From owner-freebsd-stable@FreeBSD.ORG Thu Mar 9 04:43:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE9B416A420 for ; Thu, 9 Mar 2006 04:43:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E0B43D45 for ; Thu, 9 Mar 2006 04:43:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4A1791A3C1B; Wed, 8 Mar 2006 20:43:04 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 87E8B5186D; Wed, 8 Mar 2006 23:43:03 -0500 (EST) Date: Wed, 8 Mar 2006 23:43:03 -0500 From: Kris Kennaway To: Miguel Lopes Santos Ramos Message-ID: <20060309044303.GA58022@xor.obsecurity.org> References: <20060309032802.GA57404@xor.obsecurity.org> <200603090353.k293rJ6j004298@compaq.anjos.strangled.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <200603090353.k293rJ6j004298@compaq.anjos.strangled.net> User-Agent: Mutt/1.4.2.1i Cc: kuriyama@imgsrc.co.jp, freebsd-stable@freebsd.org, kris@obsecurity.org Subject: Re: rpc.lockd brokenness (2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Mar 2006 04:43:04 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 09, 2006 at 03:53:19AM +0000, Miguel Lopes Santos Ramos wrote: > > Can you try to narrow down this problem some more? e.g. look up the > > port used by rpc.lockd with rpcinfo on client and server and tcpdump > > to see what locking requests are being passed back and forth (you > > should see the request from client -> server and the reply granting > > the lock; or not if something is going wrong). The ethereal port is > > useful for parsing the tcpdump -w -s 0 traces, btw; it decodes the RPC > > packets into human-readable form. >=20 > In the meanwhile, since my last mail, I've had some trouble finding out > the port that's used using rpcinfo. Using rpcinfo made me remember a few > things about rpc (I used it only once, some 6 years ago). I've found out > the right udp port by eliminating other options. rpcinfo -p | grep nlockmgr | grep udp > Yes, I had also checked that earlier today. I don't know if I did somethi= ng > that could have caused this... I'm almost sure it worked on 6.0 (although= not > completely, because I only got this machine working with 6 recently, it h= ad > a problem with ehci). There's no doubt it was working with 5-something. Yes, there probably were more changes since 5.x. Kris --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFED7JXWry0BWjoQKURAm//AKCZLwn32lbn6ikPMDfp3dd+XtNxagCgoQ1+ tOtams+lEZicTAJMOjiJJHg= =KAnp -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND--