From: Greg KH <gregkh@linuxfoundation.org>
To: Kuen-Han Tsai <khtsai@google.com>
Cc: prashanth.k@oss.qualcomm.com, hulianqin@vivo.com,
krzysztof.kozlowski@linaro.org, mwalle@kernel.org,
jirislaby@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] Revert "usb: gadget: u_serial: Add null pointer check in gs_start_io"
Date: Mon, 16 Jun 2025 16:18:13 +0200 [thread overview]
Message-ID: <2025061642-likeness-heaving-dd75@gregkh> (raw)
In-Reply-To: <20250616132152.1544096-1-khtsai@google.com>
On Mon, Jun 16, 2025 at 09:21:46PM +0800, Kuen-Han Tsai wrote:
> This reverts commit ffd603f214237e250271162a5b325c6199a65382.
>
> Commit ffd603f21423 ("usb: gadget: u_serial: Add null pointer check in
> gs_start_io") adds null pointer checks at the beginning of the
> gs_start_io() function to prevent a null pointer dereference. However,
> these checks are redundant because the function's comment already
> requires callers to hold the port_lock and ensure port.tty and port_usb
> are not null. All existing callers already follow these rules.
>
> The true cause of the null pointer dereference is a race condition. When
> gs_start_io() calls either gs_start_rx() or gs_start_tx(), the port_lock
> is temporarily released for usb_ep_queue(). This allows port.tty and
> port_usb to be cleared.
>
> Cc: stable@vger.kernel.org
> Fixes: ffd603f21423 ("usb: gadget: u_serial: Add null pointer check in gs_start_io")
As this is removing unneeded checks, why is it cc: stable? What bug is
being resolved here?
confused,
greg k-h
next prev parent reply other threads:[~2025-06-16 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 13:21 [PATCH 1/2] Revert "usb: gadget: u_serial: Add null pointer check in gs_start_io" Kuen-Han Tsai
2025-06-16 13:21 ` [PATCH 2/2] usb: gadget: u_serial: Fix race condition in TTY wakeup Kuen-Han Tsai
2025-06-16 14:17 ` Greg KH
2025-06-17 3:31 ` Kuen-Han Tsai
2025-06-16 14:18 ` Greg KH [this message]
2025-06-17 3:41 ` [PATCH 1/2] Revert "usb: gadget: u_serial: Add null pointer check in gs_start_io" Kuen-Han Tsai
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=2025061642-likeness-heaving-dd75@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hulianqin@vivo.com \
--cc=jirislaby@kernel.org \
--cc=khtsai@google.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=prashanth.k@oss.qualcomm.com \
--cc=stable@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