Rob Norris da33cfd436 vdev_disk_close: take disk write lock before destroying it ... Many IO operations are submitted to the kernel async, and so the zio can complete and followup actions before the submission call returns. If one of the followup actions closes the disk (eg during pool create/import), the initiator may be left holding a lock on the disk at destruction. Instead, take the write lock before finishing up and decoupling the disk state from the vdev proper. The caller will hold until all IO is submitted and locks released. Sponsored-by: Klara, Inc. Sponsored-by: Wasabi Technology, Inc. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Alexander Motin <alexander.motin@TrueNAS.com> Signed-off-by: Rob Norris <rob.norris@klarasystems.com> Closes #17719		2025-09-15 12:43:44 -07:00
..
freebsd	FreeBSD: Satisfy ASSERT_VOP_IN_SEQC()	2025-09-12 15:05:18 -07:00
linux	vdev_disk_close: take disk write lock before destroying it	2025-09-15 12:43:44 -07:00