Regression on linux-next (next-20250721)

[Borah, Chaitanya Kumar]

On 7/30/2025 4:24 PM, John Johansen wrote:
>> After bisecting the tree, the following patch [4] seems to be the 
>> first "bad" commit
>>
>> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>> commit 88fec3526e84123997ecebd6bb6778eb4ce779b7
>>
>> Author: John Johansen john.johansen at canonical.com
>>
>> Date:   Thu Jun 19 22:11:52 2025 -0700
>>
>>
>>      apparmor: make sure unix socket labeling is correctly updated.
>> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>>
>> We also verified that if we revert the patch the issue is not seen.
>>
>> Could you please check why the patch causes this regression and 
>> provide a fix if necessary?
> 
> yep thanks, fix made. That patch accidentally removed the spinlock 
> initialization from
> apparmor_file_alloc_security() while testing spin lock changes to the 
> very similar
> apparmor_sk_alloc_security(), and it wasn't caught 🙁
> 
> anyways fix is being pushed

Thank you John for your response. Kindly share the patch whenever it is 
available. So that we can verify the fix.

Regards

Chaitanya