b333z/zfs — comment on commit 2d69db27f9f459d4205050899589893dee4564bc
File:  line 0
By b333z:

No worries sounds good, I did start with that change but I pushed it down into zfs_umount_snap because the change above fixes the temp snapshot destroy in the diff, but think deleting a snapshot using zfs destroy and getting dataset not found comes from a different caller that also not setup to deal with ENOENT from zfs_unmount_snap, so we might need to identify that caller as well.

Do you know the path zfs destroy would take? I put a print_backtrace in the stap script I was using in the zfs_unmount_snap but it didn't seem to make sense and then I ran out of time and went on hol's...