Searched hist:174937 (Results 1 - 3 of 3) sorted by relevance
| /freebsd-11-stable/share/termcap/ | ||
| H A D | termcap | diff 262220 Wed Feb 19 11:09:25 MST 2014 bdrewery Add missing Save Cursor support for VT520 Submitted by: IWAMOTO Kouichi <sue@iwmt.org> PR: conf/174937 Obtained from: http://web.mit.edu/dosathena/doc/www/ek-vt520-rm.pdf Approved by: bapt (mentor) MFC after: 2 weeks |
| /freebsd-11-stable/sys/kern/ | ||
| H A D | vfs_mount.c | diff 174937 Thu Dec 27 14:38:28 MST 2007 imp A partial solution to some of the 'pull the umass device with a mounted FS' problems. These are more along the lines of 'avoiding an avoidable panic' than a complete solution to removable devices. We now close the barn door after the horse has gotten lose and has been hit by a truck, as it were. The barn no longer catches fire in this case, but the horse is still dead :-). The vfs_bio.c fix causes us not to put a failed write back into the dirty pool if the error returned was ENXIO. In that case, the buffer is treated like any other clean buffer that's being retured. ENXIO means the device isn't there anymore and will never be there again in the future, so retrying is futile. The vfs_mount.c fix treats 'ENXIO' as success for unmounting a file system. If the device is gone, retrying later won't help and we'll never be able to unmount the device. These two are part of a larger patch set submitted by the author. The other patches will be forth coming. I added comments to these two patches. Submitted by: Henrik Gulbrandsen Reviewed by: phk@ PR: usb/46176 (partial) |
| H A D | vfs_bio.c | diff 174937 Thu Dec 27 14:38:28 MST 2007 imp A partial solution to some of the 'pull the umass device with a mounted FS' problems. These are more along the lines of 'avoiding an avoidable panic' than a complete solution to removable devices. We now close the barn door after the horse has gotten lose and has been hit by a truck, as it were. The barn no longer catches fire in this case, but the horse is still dead :-). The vfs_bio.c fix causes us not to put a failed write back into the dirty pool if the error returned was ENXIO. In that case, the buffer is treated like any other clean buffer that's being retured. ENXIO means the device isn't there anymore and will never be there again in the future, so retrying is futile. The vfs_mount.c fix treats 'ENXIO' as success for unmounting a file system. If the device is gone, retrying later won't help and we'll never be able to unmount the device. These two are part of a larger patch set submitted by the author. The other patches will be forth coming. I added comments to these two patches. Submitted by: Henrik Gulbrandsen Reviewed by: phk@ PR: usb/46176 (partial) |
Completed in 316 milliseconds