Hi,

I have a patch that makes kvm_uread() read from user space using ptrace(2).

http://people.freebsd.org/~trociny/kvm_uread.ptrace.patch

With this change 'ps -e' does not requires procfs(5).

Do you like it or there might be some reasons why it is a bad idea?

Grepping sources it looks like currently only ps uses kvm_getenvv(3) (and thus
kvm_uread()).

Note, when reading from its own user space it just does bcopy(3), so if a
wrong address range is passed to kvm_uread() the program will segfault. Do we
need some protection here and what? Masking SIGSEGV?

-- 
Mikolaj Golub
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Reply via email to