summaryrefslogtreecommitdiff
path: root/drivers/md/raid5-cache.c
diff options
context:
space:
mode:
authorDmitry Torokhov <dmitry.torokhov@gmail.com>2018-08-07 01:10:40 +0300
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2018-08-08 21:23:47 +0300
commit100294cee9a98bfd4d6cb2d1c8a8aef0e959b0c4 (patch)
treebbcc4b62c252897be5c4fdb6b8f64e1ce10b1361 /drivers/md/raid5-cache.c
parent17a4ed5545c5599852a5d75c5fb2c8e597943f99 (diff)
downloadlinux-100294cee9a98bfd4d6cb2d1c8a8aef0e959b0c4.tar.xz
Input: do not use WARN() in input_alloc_absinfo()
Some of fuzzers set panic_on_warn=1 so that they can handle WARN()ings the same way they handle full-blown kernel crashes. We used WARN() in input_alloc_absinfo() to get a better idea where memory allocation failed, but since then kmalloc() and friends started dumping call stack on memory allocation failures anyway, so we are not getting anything extra from WARN(). Because of the above, let's replace WARN with dev_err(). We use dev_err() instead of simply removing message and relying on kcalloc() to give us stack dump so that we'd know the instance of hardware device to which we were trying to attach input device. Reported-by: Dmitry Vyukov <dvyukov@google.com> Acked-by: Dmitry Vyukov <dvyukov@google.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/md/raid5-cache.c')
0 files changed, 0 insertions, 0 deletions