summaryrefslogtreecommitdiffstats
path: root/lib/libgssapi/gss_unseal.c
diff options
context:
space:
mode:
authorjamie <jamie@FreeBSD.org>2009-07-30 14:28:56 +0000
committerjamie <jamie@FreeBSD.org>2009-07-30 14:28:56 +0000
commit0a7374675b784ad78bc180f06ec5e675acc4eaaa (patch)
tree4b3d544fdbba2d25a0971bcac42ff198ac0af881 /lib/libgssapi/gss_unseal.c
parent466a4af8b29f7b6d3dbab154374cfc9372f4f7ca (diff)
downloadFreeBSD-src-0a7374675b784ad78bc180f06ec5e675acc4eaaa.zip
FreeBSD-src-0a7374675b784ad78bc180f06ec5e675acc4eaaa.tar.gz
Remove a LOR, where the the sleepable allprison_lock was being obtained
in prison_equal_ip4/6 while an inp mutex was held. Locking allprison_lock can be avoided by making a restriction on the IP addresses associated with jails: Don't allow the "ip4" and "ip6" parameters to be changed after a jail is created. Setting the "ip4.addr" and "ip6.addr" parameters is allowed, but only if the jail was already created with either ip4/6=new or ip4/6=disable. With this restriction, the prison flags in question (PR_IP4_USER and PR_IP6_USER) become read-only and can be checked without locking. This also allows the simplification of a messy code path that was needed to handle an existing prison gaining an IP address list. PR: kern/136899 Reported by: Dirk Meyer Approved by: re (kib), bz (mentor)
Diffstat (limited to 'lib/libgssapi/gss_unseal.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud