Linux USB
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Lukas Wunner <lukas@wunner.de>,
	Andreas Noever <andreas.noever@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [GIT PULL] USB4/Thunderbolt fixes for v7.3-rc3
Date: Wed, 9 Sep 2026 13:12:08 +0200	[thread overview]
Message-ID: <20260909111208.GL106095@black.igk.intel.com> (raw)

Hi Greg,

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v7.3-rc3

for you to fetch changes up to e6df180e976fd08673214bc1305a46a8536aea9a:

  Revert "thunderbolt: xdomain: Notify peers after enumeration" (2026-09-04 08:28:47 +0200)

----------------------------------------------------------------
thunderbolt: Fixes for v7.3-rc3

This includes following USB4/Thunderbolt fixes:

  - Fix various issues around asynchronous DisplayPort tunnel activation
    when there is no graphics driver doing doing the capability
    exchange.
  - Fix potential NULL pointer dereference when XDomain connection is
    removed.
  - Fix use-after-free when control channel request is canceled.
  - Fix lockdep false positive.
  - Revert a commit that causes XDomain properties ping-pong.

All these have been in linux-next with no reported issues.

----------------------------------------------------------------
Fedor Pchelkin (1):
      thunderbolt: Fix NULL dereference in tb_remove_work()

Mika Westerberg (3):
      thunderbolt: Fix KASAN reported use-after-free when request is canceled
      thunderbolt: Use separate lock class for each ring
      Revert "thunderbolt: xdomain: Notify peers after enumeration"

Sven Peter (6):
      thunderbolt: Hold a router reference for each allocated HopID
      thunderbolt: Make the DP tunnel activation callback mandatory
      thunderbolt: Fix domain reference leak when DPRX read is canceled
      thunderbolt: Don't access a DP tunnel after its DPRX read was canceled
      thunderbolt: Mark discovered tunnels as active
      thunderbolt: Tear down inactive DP tunnels when the domain is stopped

 drivers/thunderbolt/ctl.c     | 63 ++++++++++++++++++-------------------
 drivers/thunderbolt/nhi.c     |  5 +++
 drivers/thunderbolt/switch.c  |  9 +++++-
 drivers/thunderbolt/tb.c      | 37 ++++++++++++++--------
 drivers/thunderbolt/test.c    | 58 +++++++++++++++++++++++++++-------
 drivers/thunderbolt/tunnel.c  | 73 ++++++++++++++++++++++++++++---------------
 drivers/thunderbolt/tunnel.h  |  8 +++--
 drivers/thunderbolt/xdomain.c |  1 -
 include/linux/thunderbolt.h   |  3 ++
 9 files changed, 170 insertions(+), 87 deletions(-)

             reply	other threads:[~2026-09-09 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 11:12 Mika Westerberg [this message]
2026-09-09 12:14 ` [GIT PULL] USB4/Thunderbolt fixes for v7.3-rc3 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:
  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=20260909111208.GL106095@black.igk.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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