[CCing a few people that afaics were involved in trying to fix the CIFS problems on 5.15/5.10 (to be honest I lost a bit track of that situation; sorry if I added too many people; at the same time I hope I did not forget anyone...)]
Anyway: it seems 5.15.149 created a new CIFS problem, see the quoted mail below for details. Ciao, Thorsten
On 26.02.24 15:28, Mohamed Abuelfotoh, Hazem wrote:
On 23/02/2024 06:14, Linux regression tracking #update (Thorsten Leemhuis) wrote:
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@eldamar.lan/
If I got this wrong and that's not the case, please holler.
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.