From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH 5.14 000/173] 5.14.10-rc2 review
Date: Tue, 5 Oct 2021 08:59:09 -0700 [thread overview]
Message-ID: <20211005155909.GA1386975@roeck-us.net> (raw)
In-Reply-To: <20211005083311.830861640@linuxfoundation.org>
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
stack backtrace:
CPU: 0 PID: 202 Comm: ip Not tainted 5.14.10-rc2-00174-g355f3195d051 #1
Call Trace:
[c000000009e27600] [c0000000008ddda8] .dump_stack_lvl+0xa4/0x100 (unreliable)
[c000000009e27690] [c000000000179b74] .debug_check_no_locks_freed+0x194/0x1b0
[c000000009e27730] [c0000000003b20e4] .kmem_cache_free+0x274/0x630
[c000000009e27800] [c000000000d04dcc] .__sk_destruct+0x18c/0x2c0
[c000000009e27890] [c000000000e67410] .udp_lib_close+0x10/0x30
[c000000009e27900] [c000000000e81628] .inet_release+0x68/0xb0
[c000000009e27980] [c000000000cf7a20] .__sock_release+0x70/0x150
[c000000009e27a10] [c000000000cf7b28] .sock_close+0x28/0x40
[c000000009e27a90] [c0000000003dbb74] .__fput+0xc4/0x310
[c000000009e27b30] [c000000000116604] .task_work_run+0xc4/0x130
[c000000009e27bd0] [c00000000001ba04] .do_notify_resume+0x414/0x4e0
[c000000009e27ce0] [c00000000002b0f4] .interrupt_exit_user_prepare_main+0x254/0x2d0
[c000000009e27d90] [c00000000002b4f4] .syscall_exit_prepare+0x74/0x120
[c000000009e27e10] [c00000000000c258] system_call_common+0xf8/0x250
--- interrupt: c00 at 0x3fff811c618c
NIP: 00003fff811c618c LR: 0000000010039e7c CTR: 0000000000000000
REGS: c000000009e27e80 TRAP: 0c00 Not tainted (5.14.10-rc2-00174-g355f3195d051)
MSR: 800000000000f032 <SF,EE,PR,FP,ME,IR,DR,RI> CR: 22000882 XER: 00000000
IRQMASK: 0
GPR00: 0000000000000006 00003fffcc4b33f0 00003fff812bf300 0000000000000000
GPR04: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR12: 0000000000000000 00003fff81335810 00000000101025a8 0000000000000000
GPR16: 0000000000000000 00003ffffcbd1e20 00000000100cbb46 00000000100cbb4e
GPR20: 00000000100c9139 00000000100cbadb 0000000000000000 0000000000000000
GPR24: ffffffffffffffff ffffffffffffffff ffffffffffffffff 00003fffcc4b3f7a
GPR28: 0000000000000000 0000000000000001 0000000000000009 0000000000000003
NIP [00003fff811c618c] 0x3fff811c618c
LR [0000000010039e7c] 0x10039e7c
next prev parent reply other threads:[~2021-10-05 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 8:38 [PATCH 5.14 000/173] 5.14.10-rc2 review Greg Kroah-Hartman
2021-10-05 13:50 ` Jon Hunter
2021-10-05 13:52 ` Fox Chen
2021-10-05 15:59 ` Guenter Roeck [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=20211005155909.GA1386975@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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