From: skunberg.kelsey at gmail.com (Kelsey Skunberg)
Subject: [Linux-kernel-mentees] [SYZBOT REPORT] WARNING: Support for this device (Terratec Grabster AV400) is experimental
Date: Fri, 17 May 2019 11:32:22 -0600 [thread overview]
Message-ID: <20190517173220.GC5873@asus> (raw)
This is a duplicate in order to cc Shuah.
WARNING: Support for this device (Terratec Grabster AV400) is experimental.
https://syzkaller.appspot.com/bug?id=faae4720a75cadb8cd0dbda5c4d3542228d37340
This warning does not trigger a crash in the system and alternatively is
warning the device?s functionality might not be entirely working.
Since this isn?t a crash, it?s incorrectly being reported in Syzbot.
I was not able to reproduce this warning due to not having the Terratec Grabster
AV400, however, by checking the following file it can be verified if the Warning
will be triggered or not:
/drivers/media/usb/pvrusb2/pvrusb2-hdw.c
I was able to verify in kernel 5.1.2, it shows the warning would be trigged due to
the following line in pvrusb2-hdw.c:
pvr2_trace(PVR2_TRACE_INFO,
"WARNING: Support for this device (%s) is experimental.",
hdw_desc->description);
The "WARNING" in the format string is getting interpeted as a Warning
from WARN_ON() and then reported to syzbot.
Clarification on valid uses of WARN(), WARN_ON(), and WARN_ON_ONCE() can be found
in the following file:
include/asm-generic/bug.h
It states: "Do not include "BUG"/"WARNING" in format strings manually to make these
conditions distinguishable from kernel issues."
This error can be resolved by updating the format strings to output an
alternative to 'WARNING' which will avoid the string from being confused
with a kernel issue.
A patch was already submitted to address this problem:
https://syzkaller.appspot.com/x/patch.diff?x=1479a4b8a00000
This patch changes the "WARNING" in format strings to have "***" on each
side of the word:
Previous Line:
- "WARNING: Support for this device (%s) is experimental.",
New Line:
+ "***WARNING*** Support for this device (%s) is experimental.",
hdw_desc->description);
WARNING: multiple messages have this Message-ID (diff)
From: skunberg.kelsey@gmail.com (Kelsey Skunberg)
Subject: [Linux-kernel-mentees] [SYZBOT REPORT] WARNING: Support for this device (Terratec Grabster AV400) is experimental
Date: Fri, 17 May 2019 11:32:22 -0600 [thread overview]
Message-ID: <20190517173220.GC5873@asus> (raw)
Message-ID: <20190517173222.ZLu1WsSCtEVyL5PttYROa3e3AWKtEMY_SSx8GxmhHMI@z> (raw)
This is a duplicate in order to cc Shuah.
WARNING: Support for this device (Terratec Grabster AV400) is experimental.
https://syzkaller.appspot.com/bug?id=faae4720a75cadb8cd0dbda5c4d3542228d37340
This warning does not trigger a crash in the system and alternatively is
warning the device?s functionality might not be entirely working.
Since this isn?t a crash, it?s incorrectly being reported in Syzbot.
I was not able to reproduce this warning due to not having the Terratec Grabster
AV400, however, by checking the following file it can be verified if the Warning
will be triggered or not:
/drivers/media/usb/pvrusb2/pvrusb2-hdw.c
I was able to verify in kernel 5.1.2, it shows the warning would be trigged due to
the following line in pvrusb2-hdw.c:
pvr2_trace(PVR2_TRACE_INFO,
"WARNING: Support for this device (%s) is experimental.",
hdw_desc->description);
The "WARNING" in the format string is getting interpeted as a Warning
from WARN_ON() and then reported to syzbot.
Clarification on valid uses of WARN(), WARN_ON(), and WARN_ON_ONCE() can be found
in the following file:
include/asm-generic/bug.h
It states: "Do not include "BUG"/"WARNING" in format strings manually to make these
conditions distinguishable from kernel issues."
This error can be resolved by updating the format strings to output an
alternative to 'WARNING' which will avoid the string from being confused
with a kernel issue.
A patch was already submitted to address this problem:
https://syzkaller.appspot.com/x/patch.diff?x=1479a4b8a00000
This patch changes the "WARNING" in format strings to have "***" on each
side of the word:
Previous Line:
- "WARNING: Support for this device (%s) is experimental.",
New Line:
+ "***WARNING*** Support for this device (%s) is experimental.",
hdw_desc->description);
next reply other threads:[~2019-05-17 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 17:32 skunberg.kelsey [this message]
2019-05-17 17:32 ` [Linux-kernel-mentees] [SYZBOT REPORT] WARNING: Support for this device (Terratec Grabster AV400) is experimental Kelsey Skunberg
-- strict thread matches above, loose matches on Subject: below --
2019-05-17 17:26 skunberg.kelsey
2019-05-17 17:26 ` Kelsey Skunberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190517173220.GC5873@asus \
--to=unknown@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.