From: syzbot <syzbot+c71bc336c5061153b502@syzkaller.appspotmail.com>
To: bragathemanick0908@gmail.com, davem@davemloft.net,
dccp@vger.kernel.org, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [dccp?] general protection fault in dccp_write_xmit (2)
Date: Wed, 08 Nov 2023 00:03:04 -0800 [thread overview]
Message-ID: <00000000000053135d06099f84a3@google.com> (raw)
In-Reply-To: <0000000000009e122006088a2b8d@google.com>
syzbot has bisected this issue to:
commit 419ce133ab928ab5efd7b50b2ef36ddfd4eadbd2
Author: Paolo Abeni <pabeni@redhat.com>
Date: Wed Oct 11 07:20:55 2023 +0000
tcp: allow again tcp_disconnect() when threads are waiting
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=142a647b680000
start commit: ff269e2cd5ad Merge tag 'net-next-6.7-followup' of git://gi..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=162a647b680000
console output: https://syzkaller.appspot.com/x/log.txt?x=122a647b680000
kernel config: https://syzkaller.appspot.com/x/.config?x=53cdcbf124ea14aa
dashboard link: https://syzkaller.appspot.com/bug?extid=c71bc336c5061153b502
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142bff40e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1559f190e80000
Reported-by: syzbot+c71bc336c5061153b502@syzkaller.appspotmail.com
Fixes: 419ce133ab92 ("tcp: allow again tcp_disconnect() when threads are waiting")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-08 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 13:09 [syzbot] [dccp?] general protection fault in dccp_write_xmit (2) syzbot
2023-11-06 22:52 ` syzbot
2023-11-08 8:03 ` syzbot [this message]
2023-12-14 12:43 ` [syzbot] Test for c71bc336c5061153b502 syzbot
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 12:08 [syzbot] [dccp?] general protection fault in dccp_write_xmit (2) xingwei lee
[not found] <20231214.214313.1429518668067958908.syoshida@redhat.com>
2023-12-14 13:25 ` 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=00000000000053135d06099f84a3@google.com \
--to=syzbot+c71bc336c5061153b502@syzkaller.appspotmail.com \
--cc=bragathemanick0908@gmail.com \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.