linux-kernel - Re: [PATCH 5.14 000/173] 5.14.10-rc2 review

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4ecdfb07-4957-913a-6bd3-4410bd2cb5c0@iki.fi>
Date:   Tue, 5 Oct 2021 22:07:43 +0300
From:   Thomas Backlund <tmb@....fi>
To:     Guenter Roeck <linux@...ck-us.net>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
        f.fainelli@...il.com, stable@...r.kernel.org
Subject: Re: [PATCH 5.14 000/173] 5.14.10-rc2 review

Den 2021-10-05 kl. 18:59, skrev Guenter Roeck:
> On Tue, Oct 05, 2021 at 10:38:40AM +0200, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 5.14.10 release.
>> There are 173 patches in this series, all will be posted as a response
>> to this one.  If anyone has any issues with these being applied, please
>> let me know.
>>
>> Responses should be made by Thu, 07 Oct 2021 08:32:44 +0000.
>> Anything received after that time might be too late.
>>
> 
> AFAICS the warning problems are still seen. Unfortunately I won't be able
> to bisect since I have limited internet access.
> 
> Guenter
> 
> =========================
> WARNING: held lock freed!
> 5.14.10-rc2-00174-g355f3195d051 #1 Not tainted
> -------------------------
> ip/202 is freeing memory c000000009918900-c000000009918f7f, with a lock still held there!
> c000000009918a20 (sk_lock-AF_INET){+.+.}-{0:0}, at: .sk_common_release+0x4c/0x1b0
> 2 locks held by ip/202:
>   #0: c00000000ae149d0 (&sb->s_type->i_mutex_key#5){+.+.}-{3:3}, at: .__sock_release+0x4c/0x150
>   #1: c000000009918a20 (sk_lock-AF_INET){+.+.}-{0:0}, at: .sk_common_release+0x4c/0x1b0
> 
> 


Isn't this a fallout of:

queue-5.14/net-introduce-and-use-lock_sock_fast_nested.patch
that has: Fixes: 2dcb96bacce3 ("net: core: Correct the 
sock::sk_lock.owned lockdep annotations")

BUT:

$ git describe --contains 2dcb96bacce3
v5.15-rc3~30^2~26

--
Thomas