mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "D. Wythe" <alibuda@linux.alibaba.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
	Wenjia Zhang <wenjia@linux.ibm.com>,
	Jan Karcher <jaka@linux.ibm.com>,
	Tony Lu <tonylu@linux.alibaba.com>,
	Wen Gu <guwen@linux.alibaba.com>,
	linux-s390@vger.kernel.org
Cc: syzbot <syzbot+e929093395ec65f969c7@syzkaller.appspotmail.com>,
	coreteam@netfilter.org, davem@davemloft.net, edumazet@google.com,
	horms@verge.net.au, ja@ssi.bg, kadlec@netfilter.org,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org, pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [lvs?] possible deadlock in start_sync_thread
Date: Wed, 6 Nov 2024 18:01:28 +0800	[thread overview]
Message-ID: <c9a1c5c5-58dc-48d0-9693-0ae4ac347b97@linux.alibaba.com> (raw)
In-Reply-To: <ZyoAjPBjtQA6jE-8@calendula>



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/




      reply	other threads:[~2024-11-06 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-24 15:27 syzbot
2024-11-02  0:20 ` syzbot
2024-11-05 11:25   ` Pablo Neira Ayuso
2024-11-06 10:01     ` D. Wythe [this message]

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=c9a1c5c5-58dc-48d0-9693-0ae4ac347b97@linux.alibaba.com \
    --to=alibuda@linux.alibaba.com \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guwen@linux.alibaba.com \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=jaka@linux.ibm.com \
    --cc=kadlec@netfilter.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    --cc=syzbot+e929093395ec65f969c7@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=wenjia@linux.ibm.com \
    /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®