linux-kernel - Re: [PATCH v3] Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <GFrqLPSzlfDdtFVUTPC7SJgyvzo5-3iiu9t3nN0uxRe4hDjFtHvYlYolo4Y3uqGlcOgyj3xT8hCch66lBLVmiG-li3rzC8G0xvqqSRTeJbo=@proton.me>
Date: Wed, 26 Nov 2025 05:14:15 +0000
From: incogcyberpunk@...ton.me
To: Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc: patchwork-bot+bluetooth@...nel.org, Doug Anderson <dianders@...omium.org>, marcel@...tmann.org, matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com, regressions@...mhuis.info, regressions@...ts.linux.dev, johan.hedberg@...il.com, sean.wang@...iatek.com, stable@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v3] Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref

Hi, 

Don't want to add trouble, just out of curiosity.

What is normally the route for patches to get into the mainline kernel? 

Isn't it as follows , as suggested in the documentations ? 
subsystem -> -next -> mainline -> stable ? 

What's this net tree , and how are the patches cherrypicked onto the  mainline kernel? is there a certain process? 

Regards, 
IncogCyberpunk