The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+96046021045ffe6d7709@syzkaller.appspotmail.com>
To: allison.henderson@oracle.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [rds?] general protection fault in rds_tcp_accept_one
Date: Mon, 09 Feb 2026 23:07:05 -0800	[thread overview]
Message-ID: <698ad919.050a0220.1ad825.0061.GAE@google.com> (raw)
In-Reply-To: <e40e70e09587fa53aa2c098739a5304d02b3ddb6.camel@oracle.com>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to checkout kernel repo git@github.com:allisonhenderson/rds_work.git/rds_tcp_bug_fixes_v14: failed to run ["git" "fetch" "--force" "75c633a41ce4e3e077c06b68250156dd34977923" "rds_tcp_bug_fixes_v14"]: exit status 128


Tested on:

commit:         [unknown 
git tree:       git@github.com:allisonhenderson/rds_work.git rds_tcp_bug_fixes_v14
kernel config:  https://syzkaller.appspot.com/x/.config?x=ac78ce3b6729749e
dashboard link: https://syzkaller.appspot.com/bug?extid=96046021045ffe6d7709
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1168ea52580000


       reply	other threads:[~2026-02-10  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e40e70e09587fa53aa2c098739a5304d02b3ddb6.camel@oracle.com>
2026-02-10  7:07 ` syzbot [this message]
     [not found] <ad80999d02b961d11160b3b6b41529f7b3bb24ca.camel@oracle.com>
2026-02-10  8:10 ` [syzbot] [rds?] general protection fault in rds_tcp_accept_one syzbot
     [not found] <3a571094912e42265974a30b4e1185511a4b81fb.camel@oracle.com>
2026-02-10  4:06 ` syzbot
     [not found] <5b60755d25c9c27c3bb6f76f051cf2b0b4322e46.camel@oracle.com>
2026-02-10  2:02 ` syzbot
2026-02-09 15:41 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=698ad919.050a0220.1ad825.0061.GAE@google.com \
    --to=syzbot+96046021045ffe6d7709@syzkaller.appspotmail.com \
    --cc=allison.henderson@oracle.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox