From: syzbot <syzbot+cd16e79c1e45f3fe0377@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, geliang@kernel.org,
horms@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org,
martineau@kernel.org, matttbe@kernel.org, mptcp@lists.linux.dev,
netdev@vger.kernel.org, pabeni@redhat.com,
stable@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mptcp?] WARNING in mptcp_pm_nl_set_flags (2)
Date: Fri, 24 Jan 2025 05:43:04 -0800 [thread overview]
Message-ID: <679398e8.050a0220.2eae65.001d.GAE@google.com> (raw)
In-Reply-To: <6786ac51.050a0220.216c54.00a6.GAE@google.com>
syzbot has bisected this issue to:
commit 322ea3778965da72862cca2a0c50253aacf65fe6
Author: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Date: Mon Aug 19 19:45:26 2024 +0000
mptcp: pm: only mark 'subflow' endp as available
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14f0bab0580000
start commit: d1bf27c4e176 dt-bindings: net: pse-pd: Fix unusual charact..
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=16f0bab0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=12f0bab0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1c541fa8af5c9cc7
dashboard link: https://syzkaller.appspot.com/bug?extid=cd16e79c1e45f3fe0377
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11262218580000
Reported-by: syzbot+cd16e79c1e45f3fe0377@syzkaller.appspotmail.com
Fixes: 322ea3778965 ("mptcp: pm: only mark 'subflow' endp as available")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-01-24 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 18:26 [syzbot] [mptcp?] WARNING in mptcp_pm_nl_set_flags (2) syzbot
2025-01-24 13:43 ` syzbot [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=679398e8.050a0220.2eae65.001d.GAE@google.com \
--to=syzbot+cd16e79c1e45f3fe0377@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--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=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.