mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: syzbot <syzbot+5a01c3a666e726bc8752@syzkaller.appspotmail.com>,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	linux-kernel@vger.kernel.org, martineau@kernel.org,
	matttbe@kernel.org, mptcp@lists.linux.dev,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mptcp?] WARNING in mptcp_check_listen_stop
Date: Thu, 14 Dec 2023 16:18:27 +0100	[thread overview]
Message-ID: <4837d1401e1610764eeea7446280de87d51912f6.camel@redhat.com> (raw)
In-Reply-To: <000000000000703582060c68aeab@google.com>

On Wed, 2023-12-13 at 10:53 -0800, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    2513974cc3e1 Merge branch 'stmmac-bug-fixes'
> git tree:       net
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=116337fae80000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=b50bd31249191be8
> dashboard link: https://syzkaller.appspot.com/bug?extid=5a01c3a666e726bc8752
> compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1119061ee80000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=110ca006e80000

It looks like tcp_diag_destroy is closing the listener subflow, while
the mptcp stack is not expecting anyone to touch it while in listener
status. I guess we can relax the mptcp_check_listen_stop checks.

/P 


  reply	other threads:[~2023-12-14 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 18:23 syzbot
2023-12-13 18:53 ` syzbot
2023-12-14 15:18   ` Paolo Abeni [this message]
2023-12-15  3:20 ` syzbot

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=4837d1401e1610764eeea7446280de87d51912f6.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+5a01c3a666e726bc8752@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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®