All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Benoît Sevens" <bsevens@google.com>, "Sasha Levin" <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y] ALSA: usb-audio: Fix out of bounds reads when finding clock sources
Date: Thu,  5 Dec 2024 08:34:08 -0500	[thread overview]
Message-ID: <20241205065732-e7e6763aef9f6e97@stable.kernel.org> (raw)
In-Reply-To: <20241205092925.922510-1-bsevens@google.com>

[ Sasha's backport helper bot ]

Hi,

Found matching upstream commit: a3dd4d63eeb452cfb064a13862fb376ab108f6a6

WARNING: Author mismatch between patch and found commit:
Backport author: "=?UTF-8?q?Beno=C3=AEt=20Sevens?=" <bsevens@google.com>
Commit author: Takashi Iwai <tiwai@suse.de>


Status in newer kernel trees:
6.12.y | Present (different SHA1: 164800d08b1a)
6.11.y | Present (different SHA1: 827fb529653f)
6.6.y | Present (different SHA1: e257c95fc2e3)
6.1.y | Present (different SHA1: 88bbac17b356)
5.15.y | Present (different SHA1: a53c8f496d27)
5.10.y | Not found

Note: The patch differs from the upstream commit:
---
1:  a3dd4d63eeb45 < -:  ------------- ALSA: usb-audio: Fix out of bounds reads when finding clock sources
-:  ------------- > 1:  ffc4b5492cccd ALSA: usb-audio: Fix out of bounds reads when finding clock sources
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y       |  Success    |  Success   |

      parent reply	other threads:[~2024-12-05 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  9:29 [PATCH 5.10.y] ALSA: usb-audio: Fix out of bounds reads when finding clock sources Benoît Sevens
2024-12-05  9:48 ` Greg KH
2024-12-05 13:34 ` Sasha Levin [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=20241205065732-e7e6763aef9f6e97@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=bsevens@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.