From owner-freebsd-stable@FreeBSD.ORG Sat Apr 8 13:52:39 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 48AB416A403 for ; Sat, 8 Apr 2006 13:52:39 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C45F43D60 for ; Sat, 8 Apr 2006 13:52:36 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by zproxy.gmail.com with SMTP id s1so568104nze for ; Sat, 08 Apr 2006 06:52:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=U5bBiWJjZywg0Kad6QDW2pyP6XJJ6Id+wweBHVAr8Dm5BVrXZfSlS3JADP7N/6unEDJPUsa+p5xlxtYTlgcMJG21s6g995gCRLznrAQqFemiSpSrsWjHz1etOcqM8T3hmChSd4lJPxtgcBVYQ/7CG48GaRdmgDXKkUHTNY2q7l4= Received: by 10.36.80.7 with SMTP id d7mr3234812nzb; Sat, 08 Apr 2006 06:52:35 -0700 (PDT) Received: by 10.36.57.15 with HTTP; Sat, 8 Apr 2006 06:52:35 -0700 (PDT) Message-ID: <6eb82e0604080652s651eeba8q7b8219f093db9f6a@mail.gmail.com> Date: Sat, 8 Apr 2006 09:52:35 -0400 From: "Rong-En Fan" To: "Kris Kennaway" In-Reply-To: <20060408060634.GA4187@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7mveururc6.wl%kuriyama@imgsrc.co.jp> <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> <20060408060634.GA4187@xor.obsecurity.org> 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 13:52:39 -0000 On 4/8/06, Kris Kennaway wrote: > 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 wit= h > > > 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! > > > > Hi, > > > > 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. > > > > 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. > > > > 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. Yes , I know that. But how to explain that after back-out 1.18 and restart rpc.lockd, my mutt and irssi will work. And putting it back, they dont work? I tried backing out and putting back three times. And, if I simply restart lockd, it does not help. Rong-En Fan