kern/126368: Running ktrace/kdump in jail leads to stale jails

[Nejc Skoberne]

>Number:         126368
>Category:       kern
>Synopsis:       Running ktrace/kdump in jail leads to stale jails
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 08 13:10:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Nejc Skoberne
>Release:        7-STABLE
>Organization:
>Environment:
FreeBSD server.domain.com 7.0-STABLE FreeBSD 7.0-STABLE #3: Mon Aug  4 10:28:12 CEST 2008     root at server.domain.com:/usr/src/sys/amd64/compile/ARLEQUIN  amd64
>Description:
Looks like running ktrace and (or?) kdump in jail isn't a very good idea. When trying to make "/etc/rc.d/jail stop jailname", the jail looks it is stopped, but the entry remains when listing jails with "jls". If the jail is run again, there will be two entries in jls output.
>How-To-Repeat:
1. Run ktrace/kdump in a jail,
2. /etc/rc.d/jail stop
3. jls output still contains the entry for that jail.
4. if running /etc/rc.d/jail start, there will be two entries for the same jail, the "broken" one will not work.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: