From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 22 20:51:03 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F317974F for ; Sun, 22 Mar 2015 20:51:03 +0000 (UTC) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9640F37C for ; Sun, 22 Mar 2015 20:51:02 +0000 (UTC) X-AuditID: 12074423-f79536d000000e74-aa-550f2a014a0e Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id E8.79.03700.10A2F055; Sun, 22 Mar 2015 16:45:53 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id t2MKjqYG006902; Sun, 22 Mar 2015 16:45:53 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t2MKjoji007668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 22 Mar 2015 16:45:52 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t2MKjoC5028417; Sun, 22 Mar 2015 16:45:50 -0400 (EDT) Date: Sun, 22 Mar 2015 16:45:50 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: Mateusz Guzik Subject: Re: How to traverse kernel threads? In-Reply-To: <20150321232622.GF14650@dft-labs.eu> Message-ID: References: <20150321220246.GE14650@dft-labs.eu> <20150321232622.GF14650@dft-labs.eu> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupmleLIzCtJLcpLzFFi42IRYrdT0WXU4g81eNCpaLF98z9Gi8aDi1ks Dh8+werA7DHj03wWj52z7rIHMEVx2aSk5mSWpRbp2yVwZaz728pScISpYtUDwQbG34xdjJwc EgImEjdev2aGsMUkLtxbz9bFyMUhJLCYSWLh/oeMEM5GRokJm5axQjiHmCQOTPgJ5TQwSvS+ mwvWzyKgLfG1dQ3YXDYBNYnHe5tZIeYqSmw+NQmsRkRAVeL50fVgcWaBNIknr26C1QsL6Ei0 X5kJZnMKGEp0z+kCs3kFHCU6pz+Euuk+o8SrA/1MIAlRoIbV+6ewQBQJSpyc+YQFYqiWxPLp 21gmMArNQpKahSS1gJFpFaNsSm6Vbm5iZk5xarJucXJiXl5qka6ZXm5miV5qSukmRnA4uyjv YPxzUOkQowAHoxIPr0IuX6gQa2JZcWXuIUZJDiYlUd7tD4FCfEn5KZUZicUZ8UWlOanFhxgl OJiVRHjfSPCHCvGmJFZWpRblw6SkOViUxHk3/eALERJITyxJzU5NLUgtgsnKcHAoSfCu0wBq FCxKTU+tSMvMKUFIM3FwggznARqurwkyvLggMbc4Mx0if4pRl+POlP+LmIRY8vLzUqXEeReD DBIAKcoozYObA0tDrxjFgd4S5pUCGcUDTGFwk14BLWECWnIunw9kSUkiQkqqgVHUfIZmoMZW hU6dtMXqN5iCnhWf0Zn+fFHyTAbzxuJLhdeP3zVsTzvbadY5Mykr+o/UZKt0445/q72Vr35s NnpypavyQo+u5JN4W92/M570h4h+yPqZEh+dq/PILfiKmnaSpfsGlSTH4hc7Lqx4+ixkjY50 2uUDlnOmJ+w503m9MTfD7kPXaSWW4oxEQy3mouJEAJiDhOIeAwAA Cc: "freebsd-hackers@freebsd.org" , Yue Chen X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2015 20:51:04 -0000 On Sat, 21 Mar 2015, Mateusz Guzik wrote: > But once more the real question is what are you trying to do. I don't > see any use for stack info of random threads. One thing that comes to mind is for live binary-patching the kernel, to confirm that no thread is currently in a routine which would be patched. -Ben