public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c71bc336c5061153b502@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syoshida@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [dccp?] general protection fault in dccp_write_xmit (2)
Date: Thu, 14 Dec 2023 05:25:04 -0800	[thread overview]
Message-ID: <0000000000002b4c3c060c783635@google.com> (raw)
In-Reply-To: <20231214.214313.1429518668067958908.syoshida@redhat.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+c71bc336c5061153b502@syzkaller.appspotmail.com

Tested on:

commit:         5bd7ef53 Merge tag 'pull-fixes' of git://git.kernel.or..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=154b3ffee80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6597c2e8d31ac85f
dashboard link: https://syzkaller.appspot.com/bug?extid=c71bc336c5061153b502
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10d75c06e80000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2023-12-14 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231214.214313.1429518668067958908.syoshida@redhat.com>
2023-12-14 13:25 ` syzbot [this message]
2023-12-11 12:08 [syzbot] [dccp?] general protection fault in dccp_write_xmit (2) xingwei lee
  -- strict thread matches above, loose matches on Subject: below --
2023-10-25 13:09 syzbot
2023-11-06 22:52 ` syzbot
2023-11-08  8:03 ` 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=0000000000002b4c3c060c783635@google.com \
    --to=syzbot+c71bc336c5061153b502@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syoshida@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox