archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <>
To: Linux regressions mailing list <>
Cc: Heikki Krogerus <>,,
	Stephan Bolten <>,
Subject: Re: [PATCH] usb: typec: ucsi: Fix command cancellation
Date: Tue, 13 Jun 2023 17:09:37 +0200	[thread overview]
Message-ID: <2023061313-headed-stumble-cf30@gregkh> (raw)
In-Reply-To: <>

On Tue, Jun 13, 2023 at 04:51:58PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 06.06.23 13:58, Heikki Krogerus wrote:
> > The Cancel command was passed to the write callback as the
> > offset instead of as the actual command which caused NULL
> > pointer dereference.
> > 
> > Reported-by: Stephan Bolten <>
> > Closes:
> > Fixes: 094902bc6a3c ("usb: typec: ucsi: Always cancel the command if PPM reports BUSY condition")
> > Cc:
> > Signed-off-by: Heikki Krogerus <>
> Gentle reminder that this made no progress for a week now. Or was there
> and I just missed it? Then apologies in advance.

This just landed in my usb-linus branch a few hours before you sent
this, and will show up in linux-next tomorrow as:
	c4a8bfabefed ("usb: typec: ucsi: Fix command cancellation")

> I'm asking, as it afaics would be nice to have this (or some other fix
> for the regression linked above) mainlined before the next -rc. That
> would be ideal, as then it can get at least one week of testing before
> the final is released.

It will get there, sorry for the delay, now caught up on all pending USB
and TTY/serial fixes.

greg k-h

       reply	other threads:[~2023-06-13 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2023-06-13 15:09   ` Greg Kroah-Hartman [this message]
2023-06-13 15:36     ` [PATCH] usb: typec: ucsi: Fix command cancellation Linux regression tracking (Thorsten Leemhuis)
2023-06-13 16:24       ` Greg Kroah-Hartman

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2023061313-headed-stumble-cf30@gregkh \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).