From owner-freebsd-stable@FreeBSD.ORG  Wed Mar  8 00:30:09 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 3EF0B16A420
	for <freebsd-stable@freebsd.org>; Wed,  8 Mar 2006 00:30:09 +0000 (GMT)
	(envelope-from miguel@anjos.strangled.net)
Received: from compaq.anjos.strangled.net (87-196-228-141.net.novis.pt
	[87.196.228.141])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 64A4343D48
	for <freebsd-stable@freebsd.org>; Wed,  8 Mar 2006 00:30:07 +0000 (GMT)
	(envelope-from miguel@anjos.strangled.net)
Received: from compaq.anjos.strangled.net (localhost [127.0.0.1])
	by compaq.anjos.strangled.net (8.13.4/8.13.4) with ESMTP id
	k280U3Tu003732; Wed, 8 Mar 2006 00:30:03 GMT
	(envelope-from miguel@compaq.anjos.strangled.net)
Received: (from miguel@localhost)
	by compaq.anjos.strangled.net (8.13.4/8.13.4/Submit) id k280U2Yh003731; 
	Wed, 8 Mar 2006 00:30:02 GMT (envelope-from miguel)
Date: Wed, 8 Mar 2006 00:30:02 GMT
From: Miguel Lopes Santos Ramos <miguel@anjos.strangled.net>
Message-Id: <200603080030.k280U2Yh003731@compaq.anjos.strangled.net>
To: kris@obsecurity.org
In-Reply-To: <20060307224337.GA28034@xor.obsecurity.org>
Cc: kuriyama@imgsrc.co.jp, freebsd-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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Mar 2006 00:30:09 -0000

> From: Kris Kennaway <kris@obsecurity.org>
> Subject: Re: rpc.lockd brokenness (2)
>
[...]
> but there's no evidence in the trace that it ever tries to write.  Can
> you also obtain a ktrace -i dump from cron?

The file remains empty.
I really don't know enough about NFS, but isn't that getattr message repeated
some seconds latter, and repeated... (even though it always gets an answer)

The ktrace is in http://mega.ist.utl.pt/~mlsr/ktrace.txt

I'm not sure it's good. I can't see cron.pid there.
I had to reboot to end the process, otherwise I couldn't kill cron and
the trace didn't grow either.

> Also while you're there, could you obtain a binary format tcpdump
> (tcpdump -w) instead?  This may be parsed with tools like ethereal
> which will help with the analysis.

The tcpdump -w is in http://mega.ist.utl.pt/~mlsr/nfs.bin

Thank you
----
Miguel Ramos