efi: Update stale locking comment for struct efivars

The comment describing how struct efivars->lock is used hasn't been
updated in sync with the code. Fix it.

Reported-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Mike Waychison <mikew@google.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>

diff --git a/include/linux/efi.h b/include/linux/efi.h
index 59c8acfebca79710b11ee35b28bee5cfc60119dc..efc681fd58956a33a4590e13b60de3dd242a24c3 100644 (file)
--- a/include/linux/efi.h
+++ b/include/linux/efi.h
@@ -1040,12 +1040,8 @@ struct efivar_operations {
 struct efivars {
        /*
         * ->lock protects two things:
-        * 1) ->list - adds, removals, reads, writes
-        * 2) ops.[gs]et_variable() calls.
-        * It must not be held when creating sysfs entries or calling kmalloc.
-        * ops.get_next_variable() is only called from register_efivars()
-        * or efivar_update_sysfs_entries(),
-        * which is protected by the BKL, so that path is safe.
+        * 1) efivarfs_list and efivars_sysfs_list
+        * 2) ->ops calls
         */
        spinlock_t lock;
        struct kset *kset;