Searched hist:35974 (Results 1 - 2 of 2) sorted by relevance
| /freebsd-11.0-release/sys/x86/x86/ | ||
| H A D | autoconf.c | diff 35974 Tue May 12 17:34:02 MDT 1998 bde Backed out previous commit. It is invalid to call d_ioctl() on possibly non-open devices, and we don't want to restrict dumping to swap devices anwyay. It is especially invalid to call d_ioctl() in non-process context for panics. d_psize() can be called on non-open devices, at least on non-SLICED ones that support d_dump(), and setdumpdev() has depended on this for a long time although it is probably wrong, but even d_psize() can't be called in non-process context - that's why dumpsys() depends on previously computed values although these values may be stale. The historical restriction to devices with dkpart(dev) == SWAP_PART should go away. |
| /freebsd-11.0-release/sys/kern/ | ||
| H A D | kern_shutdown.c | diff 35974 Tue May 12 17:34:02 MDT 1998 bde Backed out previous commit. It is invalid to call d_ioctl() on possibly non-open devices, and we don't want to restrict dumping to swap devices anwyay. It is especially invalid to call d_ioctl() in non-process context for panics. d_psize() can be called on non-open devices, at least on non-SLICED ones that support d_dump(), and setdumpdev() has depended on this for a long time although it is probably wrong, but even d_psize() can't be called in non-process context - that's why dumpsys() depends on previously computed values although these values may be stale. The historical restriction to devices with dkpart(dev) == SWAP_PART should go away. |
Completed in 146 milliseconds