From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 06:06:38 2006 Return-Path: X-Original-To: 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 70D1716A403 for ; Sat, 8 Apr 2006 06:06:38 +0000 (UTC) (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 F292D43D48 for ; Sat, 8 Apr 2006 06:06:35 +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 77E171A4DEC; Fri, 7 Apr 2006 23:06:35 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 926B251CF7; Sat, 8 Apr 2006 02:06:34 -0400 (EDT) Date: Sat, 8 Apr 2006 02:06:34 -0400 From: Kris Kennaway To: Rong-En Fan Message-ID: <20060408060634.GA4187@xor.obsecurity.org> References: <7mveururc6.wl%kuriyama@imgsrc.co.jp> <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: Jun Kuriyama , stable@freebsd.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: Sat, 08 Apr 2006 06:06:38 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 08, 2006 at 01:28:55AM -0400, Rong-En Fan wrote: > On 3/6/06, Jun Kuriyama wrote: > > > > I'm not yet received enough information to track rpc.lockd problem. > > > > As Kris posted before, here is a patch to backout my suspected > > commit. If someone can easily reproduce this problem, please try with > > this patch on both of server/client side of rpc.lockd (I'm not sure > > which of server/client side this affects). > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/80389 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84953 > > > > Any reports about this patch (OK or still problem) are welcome! >=20 > Hi, >=20 > Somehow I have problems with lockd after 3 boxes upgraded from > Feb's RELENG_6 to Apr 6's. One of them has problems with lockd. > For example, mutt and irssi will stuck in lockd (shown by > top). I tried to back out changes in revision 1.18 for lock_proc.c, > and do /etc/rc.d/nfslocking stop then a start. After backout it, > mutt and irssi work well. If I put 1.18 back, mutt and irssi will stuck > in lockd again. >=20 > Last month, I played with the test program/script in those two PRs, > found that revision 1.18 does not make any difference. I'm not 100% > sure the problem I encountered now is related to rev 1.18. But > it is a report that backout 1.18 really helps. >=20 > For record, all my clients involved in this mail are running RELENG_6. > Server is RELENG_5 as of March 9. Only IPv4 here, no IPv6. 1.18 was merged 15 months ago, so it cannot be the cause if you updated from Feb 2006. Kris --UugvWAfsgieZRqgk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEN1LpWry0BWjoQKURAqpiAKD0+UukIZQnJYG8BtwSKtUCb974ggCg8WIu YTPNRu38kePjgpWJOzpwH5Y= =058Y -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk--