| DESCRIPTION Under certain circumstances, a race
condition in the procfs subsystem can result in a kernel memory
fault panic.
A typical stack trace of the panic indicates that a procfs
routine invokes task_deallocate (), as in the following example:
0 boot
1 panic
2 trap
3 _XentMM
4 simple_lock
5 task_deallocate
6 procfs_lookup
7 namei
8 vn_open
9 copen
10 syscall
11 _Xsyscall
Less frequently, the panic stack trace involves a procfs routine
but does not involve task_deallocate(). The following example shows
a less typical stack.
0 stop_secondary_cpu
1 panic
2 event_timeout
3 printf
4 panic
5 trap
6 _XentMM
7 procfs_get_sighold
8 procfs_task_status
9 procfs_ioctl
10 vn_ioctl
11 procfs_ioctl_interface
12 ioctl_base
13 syscall
14 _Xsyscall
HP is providing two Early Release Patches (ERPs) to resolve the
issue.
|