Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci63ece7baead3f3ed@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: use IP_OUTNOROUTES drop reason
Date: Thu, 07 May 2026 03:30:58 -0700	[thread overview]
Message-ID: <69fc69e2.a00a0220.387fc1.0008.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] net: use IP_OUTNOROUTES drop reason
https://lore.kernel.org/all/20260507084305.2506115-1-edumazet@google.com
* [PATCH net-next 1/3] net: constify sk_skb_reason_drop() sock parameter
* [PATCH net-next 2/3] tcp: use SKB_DROP_REASON_IP_OUTNOROUTES in tcp_v6_send_response()
* [PATCH net-next 3/3] ipv6: use SKB_DROP_REASON_IP_OUTNOROUTES in inet6_csk_xmit()

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/09300ca9-b086-414e-ae6b-3da15492289e

***

kernel build error

tree:      net-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base:      dacf281771a9aed1a723b196120a0de8637910b9
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/61c49dd2-9ca0-4f21-b8c8-33ff9349a8dc/config

net/core/drop_monitor.c:1164:32: error: incompatible function pointer types passing 'void (*const)(void *, struct sk_buff *, void *, enum skb_drop_reason, struct sock *)' to parameter of type 'void (*)(void *, struct sk_buff *, void *, enum skb_drop_reason, const struct sock *)' [-Wincompatible-function-pointer-types]
net/core/drop_monitor.c:1179:29: error: incompatible function pointer types passing 'void (*const)(void *, struct sk_buff *, void *, enum skb_drop_reason, struct sock *)' to parameter of type 'void (*)(void *, struct sk_buff *, void *, enum skb_drop_reason, const struct sock *)' [-Wincompatible-function-pointer-types]
net/core/drop_monitor.c:1202:29: error: incompatible function pointer types passing 'void (*const)(void *, struct sk_buff *, void *, enum skb_drop_reason, struct sock *)' to parameter of type 'void (*)(void *, struct sk_buff *, void *, enum skb_drop_reason, const struct sock *)' [-Wincompatible-function-pointer-types]

***

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 dsahern@kernel.org edumazet@google.com eric.dumazet@gmail.com horms@kernel.org idosch@nvidia.com kuba@kernel.org kuniyu@google.com ncardwell@google.com netdev@vger.kernel.org pabeni@redhat.com]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid


                 reply	other threads:[~2026-05-07 10:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=69fc69e2.a00a0220.387fc1.0008.GAE@google.com \
    --to=syzbot+ci63ece7baead3f3ed@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox