[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c9a1c5c5-58dc-48d0-9693-0ae4ac347b97@linux.alibaba.com>
Date: Wed, 6 Nov 2024 18:01:28 +0800
From: "D. Wythe" <alibuda@...ux.alibaba.com>
To: Pablo Neira Ayuso <pablo@...filter.org>,
Wenjia Zhang <wenjia@...ux.ibm.com>, Jan Karcher <jaka@...ux.ibm.com>,
Tony Lu <tonylu@...ux.alibaba.com>, Wen Gu <guwen@...ux.alibaba.com>,
linux-s390@...r.kernel.org
Cc: syzbot <syzbot+e929093395ec65f969c7@...kaller.appspotmail.com>,
coreteam@...filter.org, davem@...emloft.net, edumazet@...gle.com,
horms@...ge.net.au, ja@....bg, kadlec@...filter.org, kuba@...nel.org,
linux-kernel@...r.kernel.org, lvs-devel@...r.kernel.org,
netdev@...r.kernel.org, netfilter-devel@...r.kernel.org, pabeni@...hat.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [lvs?] possible deadlock in start_sync_thread
On 11/5/24 7:25 PM, Pablo Neira Ayuso wrote:
> Hi,
>
> I am Cc'ing SHARED MEMORY COMMUNICATIONS (SMC) SOCKETS maintainers.
>
> Similar issue already reported by syzkaller here:
>
> https://lore.kernel.org/netdev/ZyIgRmJUbnZpzXNV@calendula/T/#mf1f03a65108226102d8567c9fb6bab98c072444c
>
> related to smc->clcsock_release_lock.
>
> I think this is a false possible lockdep considers smc->clcsock_release_lock
> is a lock of the same class sk_lock-AF_INET.
>
> Could you please advise?
>
> Thanks.
Hi Pablo,
Thank you for the reminder. We are currently working on it. The community has already submitted some
fixes[1], and we are still reviewing them.
Best wishes,
D. Wythe
[1]
https://lore.kernel.org/netdev/c2ac8e30806af319eb96f67103196b7cda22d562.1729031472.git.danielyangkang@gmail.com/
Powered by blists - more mailing lists