diff options
author | 2013-12-05 16:46:35 -0700 | |
---|---|---|
committer | 2013-12-08 18:23:42 -0800 | |
commit | d0f80f9aadf60adc4caafed0d2b01e79a315ff80 (patch) | |
tree | ae7e21c5105ca8f4454055400aa68ae9678d8029 /lib/kobject.c | |
parent | firmware: dmi-sysfs: Don't remove dmi-sysfs "raw" file explicitly (diff) | |
download | wireguard-linux-d0f80f9aadf60adc4caafed0d2b01e79a315ff80.tar.xz wireguard-linux-d0f80f9aadf60adc4caafed0d2b01e79a315ff80.zip |
firmware: dmi-sysfs: Remove "dmi" directory on module exit
With CONFIG_DEBUG_KOBJECT_RELEASE=y, removing and immediately reloading the
dmi-sysfs module causes the following warning:
sysfs: cannot create duplicate filename '/firmware/dmi'
kobject_add_internal failed for dmi with -EEXIST, don't try to register things with the same name in the same directory.
The "dmi" directory stays in sysfs until the dmi_kobj is released, and
DEBUG_KOBJECT_RELEASE delays that.
I don't think we can hit this problem in normal usage because dmi_kobj is
static and nothing outside dmi-sysfs can get a reference to it, so the
only way to delay the "dmi" release is with DEBUG_KOBJECT_RELEASE.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/kobject.c')
0 files changed, 0 insertions, 0 deletions