Reviewed by: Serapheim Dimitropoulos <[email protected]> Reviewed by: George Wilson <[email protected]>
The ZFS range locking code in zfs_rlock.c/h depends on ZPL-specific data structures, specifically znode_t. However, it's also used by the ZVOL code, which uses a "dummy" znode_t to pass to the range locking code. We should clean this up so that the range locking code is generic and can be used equally by ZPL and ZVOL, and also can be used by future consumers that may need to run in userland (libzpool) as well as the kernel. Upstream bug: DLPX-58662 You can view, comment on, or merge this pull request online at: https://github.com/openzfs/openzfs/pull/680 -- Commit Summary -- * 9689 zfs range lock code should not be zpl-specific -- File Changes -- M usr/src/cmd/ztest/ztest.c (16) M usr/src/uts/common/fs/zfs/sys/dmu.h (3) M usr/src/uts/common/fs/zfs/sys/zfs_rlock.h (69) M usr/src/uts/common/fs/zfs/sys/zfs_znode.h (14) M usr/src/uts/common/fs/zfs/zfs_rlock.c (564) M usr/src/uts/common/fs/zfs/zfs_vnops.c (54) M usr/src/uts/common/fs/zfs/zfs_znode.c (71) M usr/src/uts/common/fs/zfs/zvol.c (55) M usr/src/uts/common/io/comstar/lu/stmf_sbd/sbd_zvol.c (43) -- Patch Links -- https://github.com/openzfs/openzfs/pull/680.patch https://github.com/openzfs/openzfs/pull/680.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/openzfs/openzfs/pull/680 ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/T0ada5cf1c6037d04-M9b298510cd6a7616e4666f63 Delivery options: https://openzfs.topicbox.com/groups/developer/subscription
