git: 45a1044a53a1 - Create tag zfs-0.5.2
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 25 Jan 2023 01:25:58 UTC
The annotated tag zfs-0.5.2 has been created by allanjude:
URL: https://cgit.FreeBSD.org/src/tag/?h=zfs-0.5.2
tag zfs-0.5.2
Tagger: Brian Behlendorf <behlendorf1@llnl.gov>
TaggerDate: 2010-11-12 21:57:17 +0000
ZFS Version 0.5.2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEABECAAYFAkzduD0ACgkQCrnpkcavZYsC4QCfQkan1399tvn6qqRtJ9q9RTSp
63IAoNleFR15qrTtMLxWWu3UQnHdXQS9
=U6HP
-----END PGP SIGNATURE-----
commit 5e7affae52365f9f329cc63a53ae570352c4d993
Author: Brian Behlendorf <behlendorf1@llnl.gov>
AuthorDate: 2010-11-12 17:33:17 +0000
Commit: Brian Behlendorf <behlendorf1@llnl.gov>
CommitDate: 2010-11-12 17:33:17 +0000
Skip /dev/hpet during 'zpool import'
If libblkid does not contain ZFS support, then 'zpool import' will scan
all block devices in /dev/ to determine which ones are components of a
ZFS filesystem. It does this by opening all the devices and stat'ing
them to determine which ones are block devices. If the device turns
out not to be a block device it is skipped.
Usually, this whole process is pretty harmless (although slow). But
there are certain devices in /dev/ which must be handled in a very
specific way or your system may crash. For example, if /dev/watchdog
is simply opened the watchdog timer will be started and your system
will panic when the timer expires.
It turns out the /dev/hpet causes similiar problems although only when
accessed under a virtual machine. For some reason accessing /dev/hpet
causes qemu to crash. To address this issue this commit adds /dev/hpet
to the device blacklist, it will be skipped solely based on its name.