Revision 475feec0c41ad71cb7d02f0310e56256606b57c5 authored by Takashi Iwai on 16 December 2019, 15:12:24 UTC, committed by Takashi Iwai on 16 December 2019, 15:36:04 UTC
We made the error message for the CORB/RIRB communication clearer by
upgrading to dev_WARN() so that user can notice better.  But this
struck us like a boomerang: now it caught syzbot and reported back as
a fatal issue although it's not really any too serious bug that worth
for stopping the whole system.

OK, OK, let's be softy, downgrade it to the standard dev_err() again.

Fixes: dd65f7e19c69 ("ALSA: hda - Show the fatal CORB/RIRB error more clearly")
Reported-by: syzbot+b3028ac3933f5c466389@syzkaller.appspotmail.com
Link: https://lore.kernel.org/r/20191216151224.30013-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
1 parent 6fd739c
History
File Mode Size
apparmor
integrity
keys
loadpin
lockdown
safesetid
selinux
smack
tomoyo
yama
Kconfig -rw-r--r-- 10.7 KB
Kconfig.hardening -rw-r--r-- 7.9 KB
Makefile -rw-r--r-- 1.2 KB
commoncap.c -rw-r--r-- 38.9 KB
device_cgroup.c -rw-r--r-- 20.5 KB
inode.c -rw-r--r-- 10.6 KB
lsm_audit.c -rw-r--r-- 10.6 KB
min_addr.c -rw-r--r-- 1.3 KB
security.c -rw-r--r-- 59.1 KB

back to top