• Eric W. Biederman's avatar
    fs_pin: Allow for the possibility that m_list or s_list go unused. · 820f9f14
    Eric W. Biederman authored
    This is needed to support lazily umounting locked mounts.  Because the
    entire unmounted subtree needs to stay together until there are no
    users with references to any part of the subtree.
    
    To support this guarantee that the fs_pin m_list and s_list nodes
    are initialized by initializing them in init_fs_pin allowing
    for the possibility that pin_insert_group does not touch them.
    
    Further use hlist_del_init in pin_remove so that there is
    a hlist_unhashed test before the list we attempt to update
    the previous list item.
    Signed-off-by: 's avatar"Eric W. Biederman" <ebiederm@xmission.com>
    820f9f14
fs_pin.h 580 Bytes