In Message <20030927184820.W4342@snowdrop.l8s.co.uk> ,
   David Laight <david@l8s.co.uk> wrote:

=>> yes, lsof does define _KERNEL to get to that stuff, and a lot of other
=>> stuff, too.  drat.  that means i have to go fix lsof again.  well, at
=>> least this is all happening close together temporally...
=>
=>Should we have a KMEM_USER that makes some kernel structures visible to
=>certain userland programs (ie the kmem grovellers) so that almost all
=>the kernel internals can be inside _KERNEL?

   In the case of lsof, at least, doing proper sysctls for the
information of interest would probably be best, though a bit time
consuming. It would take care of the LOCKDEBUG problem, too.

   On a broader note, is kmem grovelling really a supportable
pattern going forward, or is it better off deprecated? It certainly
seems to bring up more than its share of problems.

					Gary Duzan