All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Felix Fietkau <nbd@nbd.name>,
	Lorenzo Bianconi <lorenzo@kernel.org>,
	Ryder Lee <ryder.lee@mediatek.com>,
	Shayne Chen <shayne.chen@mediatek.com>,
	Sean Wang <sean.wang@mediatek.com>,
	"open list:MEDIATEK MT76 WIRELESS LAN DRIVER"
	<linux-wireless@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>,
	regressions@lists.linux.dev
Subject: Re: strnlen buffer overflow in mt76_connac2_load_patch - 6.19-rc2
Date: Wed, 7 Jan 2026 03:57:26 +0100	[thread overview]
Message-ID: <aV3LlrckZUqdvJMG@mail-itl> (raw)
In-Reply-To: <6beab0bb-ed51-491a-bd64-15f3455ea628@leemhuis.info>

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

On Mon, Jan 05, 2026 at 02:44:28PM +0100, Thorsten Leemhuis wrote:
> On 12/27/25 21:31, Marek Marczykowski-Górecki wrote:
> > Hi,
> > 
> > After updating to 6.19-rc2 I'm hitting the following panic on boot. It
> > worked in 6.18.2. It is a Xen HVM domU with PCI device attached, this
> > one specifically:
> > 
> > 02:00.0 Network controller [0280]: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz [14c3:0608]
> >
> > And the crash is:
> 
> This looks somewhat similar to a report from Shuah Khan and likely was
> fixed with af7809f037e6e5 ("Revert "wifi: mt76: Strip whitespace from
> build ddate"") in v6.19-rc4. Please let us known if that is not the case.

Thanks, I confirm it's fixed in 6.19-rc4.

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-01-07  2:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-27 20:31 strnlen buffer overflow in mt76_connac2_load_patch - 6.19-rc2 Marek Marczykowski-Górecki
2026-01-05 13:44 ` Thorsten Leemhuis
2026-01-07  2:57   ` Marek Marczykowski-Górecki [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=aV3LlrckZUqdvJMG@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=ryder.lee@mediatek.com \
    --cc=sean.wang@mediatek.com \
    --cc=shayne.chen@mediatek.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 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.