From: Thomas Backlund <tmb@iki.fi>
To: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.14 000/173] 5.14.10-rc2 review
Date: Tue, 5 Oct 2021 22:06:40 +0300 [thread overview]
Message-ID: <160e0fba-29d8-b775-e89c-96afa29a86c1@iki.fi> (raw)
In-Reply-To: <20211005155909.GA1386975@roeck-us.net>
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
next prev parent reply other threads:[~2021-10-05 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 8:38 Greg Kroah-Hartman
2021-10-05 13:52 ` Fox Chen
2021-10-05 15:59 ` Guenter Roeck
2021-10-05 19:06 ` Thomas Backlund [this message]
2021-10-05 19:07 ` Thomas Backlund
2021-10-05 19:42 ` Naresh Kamboju
2021-10-06 7:19 ` Greg Kroah-Hartman
2021-10-05 16:16 ` Florian Fainelli
2021-10-05 18:21 ` Shuah Khan
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=160e0fba-29d8-b775-e89c-96afa29a86c1@iki.fi \
--to=tmb@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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®