From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Anssi Hannula <anssi.hannula@bitwise.fi>,
Mathias Nyman <mathias.nyman@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] xhci: fix garbage USBSTS being logged in some cases
Date: Wed, 23 Feb 2022 10:56:14 +0200 [thread overview]
Message-ID: <fe7381b1-19bc-3b1e-50f3-0ed5c7c39e5e@linux.intel.com> (raw)
In-Reply-To: <20220222134117.34844-1-anssi.hannula@bitwise.fi>
On 22.2.2022 15.41, Anssi Hannula wrote:
> xhci_decode_usbsts() is expected to return a zero-terminated string by
> its only caller, xhci_stop_endpoint_command_watchdog(), which directly
> logs the return value:
>
> xhci_warn(xhci, "USBSTS:%s\n", xhci_decode_usbsts(str, usbsts));
>
> However, if no recognized bits are set in usbsts, the function will
> return without having called any sprintf() and therefore return an
> untouched non-zero-terminated caller-provided buffer, causing garbage
> to be output to log.
>
> Fix that by always including the raw value in the output.
>
> Note that before 4843b4b5ec64 ("xhci: fix even more unsafe memory usage
> in xhci tracing") the result effect in the failure case was different as
> a static buffer was used here, but the code still worked incorrectly.
>
> Fixes: 9c1aa36efdae ("xhci: Show host status when watchdog triggers and host is assumed dead.")
> Signed-off-by: Anssi Hannula <anssi.hannula@bitwise.fi>
> ---
>
> Noticed this while debugging a USB issue. Let me know if you prefer a
> different fix.
>
> drivers/usb/host/xhci.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
> index 8a0026ee9524..ac91647195f6 100644
> --- a/drivers/usb/host/xhci.h
> +++ b/drivers/usb/host/xhci.h
> @@ -2642,6 +2642,7 @@ static inline const char *xhci_decode_usbsts(char *str, u32 usbsts)
> ret += sprintf(str + ret, " CNR");
> if (usbsts & STS_HCE)
> ret += sprintf(str + ret, " HCE");
> + ret += sprintf(str + ret, " (0x%08x)", usbsts);
Thanks, nice catch.
Maybe this could be the first thing printed out, something like (untested):
@@ -2697,8 +2697,11 @@ static inline const char *xhci_decode_usbsts(char *str, u32 usbsts)
{
int ret = 0;
+ ret = sprintf(str, " 0x%08x", usbsts);
+
if (usbsts == ~(u32)0)
- return " 0xffffffff";
+ return str;
+
-Mathias
next prev parent reply other threads:[~2022-02-23 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 13:41 Anssi Hannula
2022-02-22 13:41 ` [PATCH 2/2] xhci: fix uninitialized string returned by xhci_decode_ctrl_ctx() Anssi Hannula
2022-02-23 8:56 ` Mathias Nyman [this message]
2022-02-25 10:26 ` [PATCH 1/2 v2] xhci: fix garbage USBSTS being logged in some cases Anssi Hannula
2022-02-28 11:34 ` Mathias Nyman
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=fe7381b1-19bc-3b1e-50f3-0ed5c7c39e5e@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=anssi.hannula@bitwise.fi \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®