From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Anssi Hannula <anssi.hannula@bitwise.fi>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 v2] xhci: fix garbage USBSTS being logged in some cases
Date: Mon, 28 Feb 2022 13:34:45 +0200 [thread overview]
Message-ID: <01054a96-22d1-b72e-1166-fcbd5c2f489b@linux.intel.com> (raw)
In-Reply-To: <20220225102602.3829106-1-anssi.hannula@bitwise.fi>
On 25.2.2022 12.26, 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>
> ---
Thanks. Adding both 1/2 v2 and 2/2
-Mathias
prev parent reply other threads:[~2022-02-28 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 13:41 [PATCH 1/2] " 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 ` [PATCH 1/2] xhci: fix garbage USBSTS being logged in some cases Mathias Nyman
2022-02-25 10:26 ` [PATCH 1/2 v2] " Anssi Hannula
2022-02-28 11:34 ` Mathias Nyman [this message]
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=01054a96-22d1-b72e-1166-fcbd5c2f489b@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 \
/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®