From owner-freebsd-hackers@FreeBSD.ORG  Thu Apr  3 08:02:25 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 17F411C2;
 Thu,  3 Apr 2014 08:02:25 +0000 (UTC)
Received: from mail.tdx.com (mail.tdx.com [62.13.128.18])
 by mx1.freebsd.org (Postfix) with ESMTP id AF5128FF;
 Thu,  3 Apr 2014 08:02:24 +0000 (UTC)
Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251])
 (authenticated bits=0)
 by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s3382MOU088669
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Thu, 3 Apr 2014 09:02:22 +0100 (BST)
Date: Thu, 03 Apr 2014 09:02:21 +0100
From: Karl Pielorz <kpielorz_lst@tdx.co.uk>
To: John Baldwin <jhb@freebsd.org>
Subject: Re: Stuck CLOSED sockets / sshd / zombies...
Message-ID: <9FDC091D98AB2CF92DE4399F@Mail-PC.tdx.co.uk>
In-Reply-To: <201404021405.56878.jhb@freebsd.org>
References: <3FE645E9723756F22EF901AE@Mail-PC.tdx.co.uk>
 <201404021130.39478.jhb@freebsd.org>
 <B03C862019293A4090837F62@study64.tdx.co.uk>
 <201404021405.56878.jhb@freebsd.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: freebsd-hackers@freebsd.org
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 08:02:25 -0000



--On 02 April 2014 14:05 -0400 John Baldwin <jhb@freebsd.org> wrote:

> Grr, I guess that's what I should have expected.  Was sort of hoping to
> be able to see which socket it was blocked on.  Can you run 'kgdb' as =
root
> (no args), then do 'proc 4346' and 'bt'?  If you are familiar with gdb,
> walk up to the frame that in sys_read and do 'p *uap' so we can see which
> fd is being read.

Ok, think I've done this right (if not, let me know what I should be doing=20
:)

"
...
(kgdb) up
#9  0xffffffff80903133 in sys_read (td=3D<value optimized out>, =
uap=3D<value=20
optimized out>) at ../../../kern/sys_generic.c:171
171             error =3D kern_readv(td, uap->fd, &auio);
(kgdb) p *uap
$1 =3D {fd_l_ =3D 0xfffff800238bb920 "\b\021I\201=C3=BF=C3=BF=C3=BF=C3=BF", =
fd =3D -2125917944,=20
fd_r_ =3D "=C3=BF=C3=BF=C3=BF=C3=BF", buf_l_ =3D 0xfffff800238bb928 "", buf =
=3D=20
0xfffff800237a1000,
  buf_r_ =3D 0xfffff800238bb930 "", nbyte_l_ =3D 0xfffff800238bb930 "", =
nbyte =3D=20
0, nbyte_r_ =3D 0xfffff800238bb938 "\020\020z#"}
"

-Karl