public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: "Katiyar, Pooja" <pooja.katiyar@linux.intel.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Pooja Katiyar <pooja.katiyar@intel.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] usb: typec: ucsi: revert broken buffer management
Date: Tue, 23 Dec 2025 15:24:24 +0100	[thread overview]
Message-ID: <2025122344-purely-subsonic-4b97@gregkh> (raw)
In-Reply-To: <aUqhgbxGIbq_V9Cz@hovoldconsulting.com>

On Tue, Dec 23, 2025 at 03:04:49PM +0100, Johan Hovold wrote:
> On Mon, Dec 22, 2025 at 02:15:10PM -0800, Katiyar, Pooja wrote:
> > On Mon, Dec 22, 2025 at 07:22:00AM -0800, Johan Hovold wrote:
> > > The new buffer management code has not been tested or reviewed properly
> > > and breaks boot of machines like the Lenovo ThinkPad X13s.
> > > 
> > > Fixing this will require designing a proper interface for managing these
> > > transactions, something which most likely involves reverting most of the
> > > offending commit anyway.
> > > 	    
> > > Revert the broken code to fix the regression and let Intel come up with
> > > a properly tested implementation for a later kernel.
> > > 
> > 
> > Thanks! A fix patch addressing the race condition has been identified and
> > is being tested right now. It will be submitted for review shortly.
> > 
> > Here’s the discussion on same - 
> > https://lore.kernel.org/all/349e1f70-7e40-4e3e-b078-6e001bbb5f1a@oss.qualcomm.com/
> 
> Yes, I'm aware that discussion and I still think this needs to be
> reverted. Then you can propose a redesigned and tested implementation
> that we can help you review as that kind of work is not something that
> should be done as part of rc stabilisation.

I agree, I don't see a submitted patch yet so I'll go take your reverts
at this point in time.  That way people have more time to get this
correct instead of being rushed this time of the year.

thanks,

greg k-h

  reply	other threads:[~2025-12-23 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22 15:22 [PATCH 0/4] usb: typec: ucsi: revert broken buffer management Johan Hovold
2025-12-22 15:22 ` [PATCH 1/4] Revert "usb: typec: ucsi: Add support for SET_PDOS command" Johan Hovold
2025-12-22 15:22 ` [PATCH 2/4] Revert "usb: typec: ucsi: Enable debugfs for message_out data structure" Johan Hovold
2025-12-22 15:22 ` [PATCH 3/4] Revert "usb: typec: ucsi: Add support for message out " Johan Hovold
2025-12-22 15:22 ` [PATCH 4/4] Revert "usb: typec: ucsi: Update UCSI structure to have message in and message out fields" Johan Hovold
2025-12-22 22:15 ` [PATCH 0/4] usb: typec: ucsi: revert broken buffer management Katiyar, Pooja
2025-12-23 14:04   ` Johan Hovold
2025-12-23 14:24     ` Greg Kroah-Hartman [this message]
2025-12-23 20:21       ` Katiyar, Pooja

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=2025122344-purely-subsonic-4b97@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pooja.katiyar@intel.com \
    --cc=pooja.katiyar@linux.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