Searched hist:211930 (Results 1 - 2 of 2) sorted by relevance
| /freebsd-11-stable/sys/sys/ | ||
| H A D | mount.h | diff 211930 Sat Aug 28 07:01:51 MDT 2010 pjd There is a bug in vfs_allocate_syncvnode() failure handling in mount code. Actually it is hard to properly handle such a failure, especially in MNT_UPDATE case. The only reason for the vfs_allocate_syncvnode() function to fail is getnewvnode() failure. Fortunately it is impossible for current implementation of getnewvnode() to fail, so we can assert this and make vfs_allocate_syncvnode() void. This in turn free us from handling its failures in the mount code. Reviewed by: kib MFC after: 1 month |
| /freebsd-11-stable/sys/kern/ | ||
| H A D | vfs_mount.c | diff 211930 Sat Aug 28 07:01:51 MDT 2010 pjd There is a bug in vfs_allocate_syncvnode() failure handling in mount code. Actually it is hard to properly handle such a failure, especially in MNT_UPDATE case. The only reason for the vfs_allocate_syncvnode() function to fail is getnewvnode() failure. Fortunately it is impossible for current implementation of getnewvnode() to fail, so we can assert this and make vfs_allocate_syncvnode() void. This in turn free us from handling its failures in the mount code. Reviewed by: kib MFC after: 1 month |
Completed in 155 milliseconds