>save/restore of lock_depth for a new, self-unlocking copy_*_user, but
>right now the droplock diffs still do the right thing the simple way.
I wouldn't call it the "right thing". It's also not simpler according to
me since to make sure that the unlock_kernel is really dropping the
kernel_flag spinlock you must check all entry paths and verify that
lock_depth is 0 at such time.
Andrea Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/