kern/180098: [rm_rlock][mac_portacl][panic] recursed on non-recursive rmlock mac_policy_rm

Peter Zehm peter at bsdenergy.net
Sat Jun 29 19:10:00 UTC 2013


>Number:         180098
>Category:       kern
>Synopsis:       [rm_rlock][mac_portacl][panic] recursed on non-recursive rmlock mac_policy_rm
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 29 19:10:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Peter Zehm
>Release:        10.0-CURRENT r252372
>Organization:
>Environment:
FreeBSD BlackSun.crush-net.local 10.0-CURRENT FreeBSD 10.0-CURRENT #13 r252372M: Sun Jun 30 01:39:32 JST 2013     root at BlackSun.crush-net.local:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
After updating from r251822 to today's r252372 my system panics on boot during the starting of services.
With disabling the loading of 'mac_portacl' in the loader promt the system starts up without problems. The problem can then be triggered manually by loading the module 'mac_portacl' and restarting a network related service of choice. (devd, cron does not trigger)

Wen triggering the panic by restarting sshd I get the following:
------
panic. rm_lock: recursed on non-recursive rmlock mac_policy_rm @ /usr/src/sys/security/mac/mac_framework.c:198

cpuid = 3
KBD: enter: panic
[ thread pid 2178 tid 100814 ]
Stopped ad      kbd_enter+0x3e: movq    $0,kdb_why
db> 
-------

I created a dump and put the bt on http://pastebin.com/pfBZtcdy

In my /etc/sysctl.conf I have the following lines regarding mac_portacl:
..
security.mac.portacl.port_high=1023
net.inet.ip.portrange.reservedlow=0
net.inet.ip.portrange.reservedhigh=0
security.mac.portacl.suser_exempt=1
security.mac.portacl.rules=uid:53:udp:53,uid:53:tcp:53
..

>From the commit log, for me r252209 looks like it could have something to do with this.

I don't know if other MAC-modules are affected, too.
>How-To-Repeat:
boot with module 'mac_portacl' enabled
 or
kldload mac_portacl && /etc/rc.d/syslogd restart (restarting any network related service is ok)
>Fix:


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


More information about the freebsd-bugs mailing list