Date: Sun, 22 Mar 2015 21:58:43 +0100 From: Oliver Pinter <oliver.pinter@hardenedbsd.org> To: Benjamin Kaduk <bjk@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Mateusz Guzik <mjguzik@gmail.com>, Yue Chen <ycyc321@gmail.com> Subject: Re: How to traverse kernel threads? Message-ID: <CAPQ4ffuszSi%2B_SopJdCkoFr4OoY9=BZVbO6oo_s0sKrn8Rgjrw@mail.gmail.com> In-Reply-To: <alpine.GSO.1.10.1503221644440.22210@multics.mit.edu> References: <CAKtBrB4h13ZFJ=V0fvkDeTG-L6=e5Uz9%2BHfYc8vY523Y3X6N0A@mail.gmail.com> <20150321220246.GE14650@dft-labs.eu> <CAKtBrB5KNqt6UJ1R_BQpPfTvQZdUzGvZZtT7Uz5qd4VrrfgEdw@mail.gmail.com> <20150321232622.GF14650@dft-labs.eu> <alpine.GSO.1.10.1503221644440.22210@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Probably take a look at DDB: https://github.com/HardenedBSD/hardenedBSD/blob/hardened/current/master/sys/ddb/db_thread.c#L88 On Sun, Mar 22, 2015 at 9:45 PM, Benjamin Kaduk <bjk@freebsd.org> wrote: > 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 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPQ4ffuszSi%2B_SopJdCkoFr4OoY9=BZVbO6oo_s0sKrn8Rgjrw>