| commit | de96e9fea7ba56042f105b6fe163447b280eb800 | |
| author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Thu, 3 Jan 2019 09:23:47 +0000 (3 10:23 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Mon, 7 Jan 2019 07:53:32 +0000 (7 08:53 +0100) | ||
| tree | d3f6f03da38d0bbe96c587e2bae9e11cb53123ed | treesnapshot (tar.gz zip) |
| parent | bfeffd155283772bbe78c6a05dec7c0128ee500c | commitdiff |
sysfs: convert BUG_ON to WARN_ON
It's rude to crash the system just because the developer did something
wrong, as it prevents them from usually even seeing what went wrong.
So convert the few BUG_ON() calls that have snuck into the sysfs code
over the years to WARN_ON() to make it more "friendly". All of these
are able to be recovered from, so it makes no sense to crash.
Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
It's rude to crash the system just because the developer did something
wrong, as it prevents them from usually even seeing what went wrong.
So convert the few BUG_ON() calls that have snuck into the sysfs code
over the years to WARN_ON() to make it more "friendly". All of these
are able to be recovered from, so it makes no sense to crash.
Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| fs/sysfs/dir.c | diffblobblamehistory | |
| fs/sysfs/file.c | diffblobblamehistory | |
| fs/sysfs/group.c | diffblobblamehistory | |
| fs/sysfs/symlink.c | diffblobblamehistory |