Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Mar 2015 16:45:50 -0400 (EDT)
From:      Benjamin Kaduk <bjk@freebsd.org>
To:        Mateusz Guzik <mjguzik@gmail.com>
Cc:        "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Yue Chen <ycyc321@gmail.com>
Subject:   Re: How to traverse kernel threads?
Message-ID:  <alpine.GSO.1.10.1503221644440.22210@multics.mit.edu>
In-Reply-To: <20150321232622.GF14650@dft-labs.eu>
References:  <CAKtBrB4h13ZFJ=V0fvkDeTG-L6=e5Uz9%2BHfYc8vY523Y3X6N0A@mail.gmail.com> <20150321220246.GE14650@dft-labs.eu> <CAKtBrB5KNqt6UJ1R_BQpPfTvQZdUzGvZZtT7Uz5qd4VrrfgEdw@mail.gmail.com> <20150321232622.GF14650@dft-labs.eu>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1503221644440.22210>