From: syzbot ci <syzbot+ciede86d426d08742b@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: rxrpc: Miscellaneous fixes
Date: Mon, 20 Apr 2026 10:19:04 -0700 [thread overview]
Message-ID: <69e66008.050a0220.24bfd3.0026.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] rxrpc: Miscellaneous fixes
https://lore.kernel.org/all/20260420145900.1223732-1-dhowells@redhat.com
* [PATCH net 1/4] rxrpc: Fix memory leaks in rxkad_verify_response()
* [PATCH net 2/4] rxrpc: Fix conn-level packet handling to unshare RESPONSE packets
* [PATCH net 3/4] rxgk: Fix potential integer overflow in length check
* [PATCH net 4/4] rxrpc: Fix rxkad crypto unalignment handling
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/63d49527-25f9-4906-be84-5e4627045955
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: 0cf004ffb61cd32d140531c3a84afe975f9fc7ea
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/e9d6cb44-e357-4a27-9cc4-bb8fc0b6439d/config
net/rxrpc/rxkad.c:1170:3: error: cannot jump from this goto statement to its label
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[davem@davemloft.net dhowells@redhat.com edumazet@google.com horms@kernel.org jaltman@auristor.com kuba@kernel.org linux-afs@lists.infradead.org linux-kernel@vger.kernel.org marc.dionne@auristor.com netdev@vger.kernel.org pabeni@redhat.com stable@kernel.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-04-20 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 17:19 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-26 15:23 [moderation/CI] Re: rxrpc: Miscellaneous fixes syzbot ci
2026-03-23 18:08 syzbot ci
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=69e66008.050a0220.24bfd3.0026.GAE@google.com \
--to=syzbot+ciede86d426d08742b@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@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.