Whoever made procfs aware of kernel threads broke also the
/proc/%pid/status line. Or, maybe it's a by-product of showing
kthreads in the proc table...

According to procfs(5), the status line contains several well-defined
fields separated by spaces. However, the kernel thread names look like
'swi5: task queue' and 'swi1: net', which results in variable number of
space-separated fields. As a consequence, some software that parses this
line gives incorrect results.

I noticed this while trying to fix mysterious coredumps in
src/release/picobsd/tinyware/aps (which is obsolete anyway, but it should

Andrzej Bialecki

//  <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com)
// -------------------------------------------------------------------
// ------ FreeBSD: The Power to Serve. http://www.freebsd.org --------
// --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ----

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to