From: Sasha Levin <sashal@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.1 0000/1887] 6.1.191-rc1 review
Date: Wed, 28 Oct 2026 22:53:18 -0400 [thread overview]
Message-ID: <81c6fc0c56aa4c83a06a.sashal-rc-0001@kernel.org> (raw)
In-Reply-To: <d989cca6-f049-4c87-bacf-8a6a4832dfbd@gmail.com>
On 10/28/26 14:26, Florian Fainelli wrote:
> On 10/28/26 14:12, Florian Fainelli wrote:
>> this is due to 341d4e6294d9 ("highmem: add memcpy_to_folio() and
>> memcpy_from_folio()"). We would need to also back port 00cdf76012ab
That one was already addressed earlier today. Rather than adding
00cdf76012ab, I dropped the highmem/hfs set from the 6.1 queue:
- highmem: add memcpy_to_folio() and memcpy_from_folio()
- highmem: fix a memory copy problem in memcpy_from_folio
- hfs: fix general protection fault in hfs_find_init()
- pagemap: add filemap_grab_folio()
> And there is this other build failure caused by 997f9c35fcad
> ("Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete")
>
> net/bluetooth/mgmt.c: In function 'set_mesh_sync':
> net/bluetooth/mgmt.c:2188:36: error: implicit declaration of function
> '__struct_size'; did you mean 'struct_size'?
The 6.1 backport of that patch uses __struct_size(), which on 6.1 is only
available with CONFIG_FORTIFY_SOURCE enabled, so it breaks the build
without it. Fixed by dropping the five-patch Bluetooth MGMT cluster from
the 6.1 queue:
- Bluetooth: MGMT: Fix possible UAFs
- Bluetooth: MGMT: Fix dangling pointer on
mgmt_add_adv_patterns_monitor_complete
- Bluetooth: MGMT: Fix memory leak in set_ssp_complete
- Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete
- Bluetooth: MGMT: Fix list corruption and UAF in command complete
handlers
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-29 2:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 16:34 Greg Kroah-Hartman
2026-10-28 17:04 ` [PATCH 6.1 1779/1887] hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur Greg Kroah-Hartman
2026-10-28 19:54 ` [PATCH 6.1 0000/1887] 6.1.191-rc1 review Brett A C Sheffield
2026-10-28 20:44 ` Brett A C Sheffield
2026-10-29 0:25 ` Peter Schneider
2026-10-29 6:17 ` Greg Kroah-Hartman
2026-10-29 8:14 ` Brett A C Sheffield
2026-10-29 8:29 ` Brett A C Sheffield
2026-10-28 21:12 ` Florian Fainelli
2026-10-28 21:26 ` Florian Fainelli
2026-10-29 2:53 ` Sasha Levin [this message]
2026-10-28 22:16 ` Pavel Machek
2026-10-29 0:19 ` Peter Schneider
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=81c6fc0c56aa4c83a06a.sashal-rc-0001@kernel.org \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®