Bug #8377

Panic in bookmark deletion

Added by Serapheim Dimitropoulos 11 months ago. Updated 10 months ago.

Status:ClosedStart date:2017-06-12
Priority:NormalDue date:
Assignee:Serapheim Dimitropoulos% Done:


Category:zfs - Zettabyte File System
Target version:-
Difficulty:Medium Tags:needs-triage


The problem is that when dsl_bookmark_destroy_check() is executed from open context (the pre-check), it fills in dbda_success based on the existence of the bookmark.
But the bookmark (or containing filesystem as in this case) can be destroyed before we get to syncing context. When we re-run dsl_bookmark_destroy_check() in syncing
context, it will not add the deleted bookmark to dbda_success, intending for dsl_bookmark_destroy_sync() to not process it. But because the bookmark is still in dbda_success
from the open-context call, we do try to destroy it.

The fix is that dsl_bookmark_destroy_check() should not modify dbda_success when called from open context.


#1 Updated by Electric Monk 10 months ago

  • % Done changed from 0 to 100
  • Status changed from New to Closed

git commit 42418f9e73f0d007aa87675ecc206c26fc8e073e

commit  42418f9e73f0d007aa87675ecc206c26fc8e073e
Author: Matthew Ahrens <mahrens@delphix.com>
Date:   2017-06-29T23:10:42.000Z

    8377 Panic in bookmark deletion
    Reviewed by: Paul Dagnelie <pcd@delphix.com>
    Reviewed by: Pavel Zakharov <pavel.zakharov@delphix.com>
    Reviewed by: George Wilson <george.wilson@delphix.com>
    Approved by: Robert Mustacchi <rm@joyent.com>

Also available in: Atom