kernel - Fix fstatfs() and fstatvfs() when called from a null-mounted chroot()
authorMatthew Dillon <dillon@apollo.backplane.com>
Fri, 1 Apr 2011 23:03:09 +0000 (16:03 -0700)
committerMatthew Dillon <dillon@apollo.backplane.com>
Fri, 1 Apr 2011 23:03:09 +0000 (16:03 -0700)
commit92734e3dc3576d68a28eb7d539dd48de730ab82d
tree6915e36b3c3df36665c43c48f18df5bebefa675e
parentf891a7e14fd5dc837613c9815d3d80cc1ca31929
kernel - Fix fstatfs() and fstatvfs() when called from a null-mounted chroot()

* These funtions were using the wrong starting mount pointer when calling
  cache_fullpath().  They were using the mount pointer for the open file's
  vnode instead of the overlay (null) mount pointer.

  This caused cache_fullpath() to believe the fd represented a file outside
  the chroot and return an error.

Reported-by: Francois Tigeot<ftigeot@wolfpond.org>:
sys/kern/vfs_syscalls.c