On 23/02/2024 06:14, Linux regression tracking #update (Thorsten
Leemhuis) wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
Thx. Took a while (among others because the stable team worked a bit
slower that usual), but from what Paulo Alcantara and Salvatore
Bonaccorso recently said everything is afaics now fixed or on track to
be fixed in all affected stable/longterm branches:
https://lore.kernel.org/all/ZdgyEfNsev8WGIl5@xxxxxxxxxxx/
If I got this wrong and that's not the case, please holler.
#regzbot resolve: apparently fixed in all affected stable/longterm
branches with various commits
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
We are seeing CIFS mount failures after upgrading from v5.15.148 to
v5.15.149, I have reverted eb3e28c1e8 ("smb3: Replace smb2pdu 1-element
arrays with flex-arrays") and I no longer see the regression. It looks
like the issue is also impacting v5.10.y as the mentioned reverted patch
has also been merged to v5.10.210. I am currently running the CIFS mount
test manually and will update the thread with the exact mount failure
error. I think we should revert eb3e28c1e8 ("smb3: Replace smb2pdu
1-element arrays with flex-arrays") from both v5.15.y & v5.10.y until we
come up with a proper fix on this versions, please note that if we will
take this path then we will need to re-introduce. b3632baa5045 ("cifs:
fix off-by-one in SMB2_query_info_init()") which has been removed from
latest v5.10.y and v5.15.y releases.
