Summary: | lsof -i panics system | ||
---|---|---|---|
Product: | Base System | Reporter: | mwlucas |
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | CC: | emaste, ler, mjg |
Priority: | --- | ||
Version: | CURRENT | ||
Hardware: | amd64 | ||
OS: | Any | ||
See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194974 |
Description
mwlucas
2014-11-13 16:05:09 UTC
let me know if I need to get Vic involved.... Larry Rosenman Maintainer, sysutils/lsof > let me know if I need to get Vic involved....
Will do; at this point I think it's not likely.
While clearly the kernel should not panic, why is lsof reading kernel memory? What interfaces (if any) are missing? As to why lsof is reading kernel memory, there are TONS of messages on various lists over the last few years. Vic has said he'd use interfaces, but no one (tmk) has written what he needs. A commit references this bug: Author: kib Date: Sat Jan 3 01:28:59 UTC 2015 New revision: 276600 URL: https://svnweb.freebsd.org/changeset/base/276600 Log: For /dev/mem and /dev/kmem accesses, avoid asserting that addresses are within direct map. We want to return error instead of panicing. PR: 194995 Sponsored by: The FreeBSD Foundation Changes: head/sys/amd64/amd64/mem.c head/sys/amd64/include/vmparam.h To originators/assignees of this PR: A commit to the tree references this PR, however the PR is still in a non-closed state. Please review this PR and close as appropriate, or if closing the PR requires a merge to stable/10, please let re@ know as soon as possible. Thank you. Glen This sure seems fixed now. Cannot reproduce on any of my systems. Now to see if I can close a bugzilla PR. :-) |