summaryrefslogtreecommitdiffstats
path: root/sys/geom/raid/g_raid.c
diff options
context:
space:
mode:
authorkib <kib@FreeBSD.org>2012-09-13 13:05:45 +0000
committerkib <kib@FreeBSD.org>2012-09-13 13:05:45 +0000
commit10608e7d855a9c973b57055bfc2e87284c68ce9e (patch)
tree4a1c7c3f5e51132eef47883a5fc11727375f8e2c /sys/geom/raid/g_raid.c
parent292a32313d952d75e33dffe6fa8ee77e8fb0ae98 (diff)
downloadFreeBSD-src-10608e7d855a9c973b57055bfc2e87284c68ce9e.zip
FreeBSD-src-10608e7d855a9c973b57055bfc2e87284c68ce9e.tar.gz
The deadfs VOPs for vop_ioctl and vop_bmap call itself recursively,
which is an elaborate way to cause kernel panic. Change the VOPs implementation to return EBADF for a reclaimed vnode. While the calls to vop_bmap should not reach deadfs, it is indeed possible for vop_ioctl, because the VOP locking protocol is to pass the vnode to VOP unlocked. The actual panic was observed when ioctl was called on procfs filedescriptor which pointed to an exited process. Reported by: zont Tested by: pho MFC after: 1 week
Diffstat (limited to 'sys/geom/raid/g_raid.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud