All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+c28dd30bc14158282b3b@syzkaller.appspotmail.com>
To: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	 kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org,  pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] [net?] WARNING in geneve_udp_encap_recv
Date: Mon, 04 Nov 2024 20:33:21 -0800	[thread overview]
Message-ID: <6729a011.050a0220.2edce.1501.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    90602c251cda Merge tag 'net-6.12-rc6' of git://git.kernel...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16519340580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4340261e4e9f37fc
dashboard link: https://syzkaller.appspot.com/bug?extid=c28dd30bc14158282b3b
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-90602c25.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6a2daa3dcb25/vmlinux-90602c25.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4488ee6eec29/bzImage-90602c25.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c28dd30bc14158282b3b@syzkaller.appspotmail.com

memcpy: detected field-spanning write (size 4) of single field "_Generic(info, const struct ip_tunnel_info * : ((const void *)((info) + 1)), struct ip_tunnel_info * : ((void *)((info) + 1)) )" at include/net/ip_tunnels.h:653 (size 0)
WARNING: CPU: 3 PID: 34 at include/net/ip_tunnels.h:653 ip_tunnel_info_opts_set include/net/ip_tunnels.h:653 [inline]
WARNING: CPU: 3 PID: 34 at include/net/ip_tunnels.h:653 geneve_rx drivers/net/geneve.c:244 [inline]
WARNING: CPU: 3 PID: 34 at include/net/ip_tunnels.h:653 geneve_udp_encap_recv+0x22cd/0x29a0 drivers/net/geneve.c:401
Modules linked in:
CPU: 3 UID: 0 PID: 34 Comm: ksoftirqd/3 Not tainted 6.12.0-rc5-syzkaller-00161-g90602c251cda #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:ip_tunnel_info_opts_set include/net/ip_tunnels.h:653 [inline]
RIP: 0010:geneve_rx drivers/net/geneve.c:244 [inline]
RIP: 0010:geneve_udp_encap_recv+0x22cd/0x29a0 drivers/net/geneve.c:401
Code: 9e e9 ff ff e8 24 ca 53 fb c6 05 c4 65 0e 0a 01 90 31 c9 48 c7 c2 e0 3e 14 8c 4c 89 e6 48 c7 c7 c0 3f 14 8c e8 c4 b9 14 fb 90 <0f> 0b 90 90 e9 c7 ed ff ff e8 f5 c9 53 fb e8 80 8c c9 02 31 ff 41
RSP: 0018:ffffc900008df630 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff888060da0f32 RCX: ffffffff814e6dd9
RDX: ffff88801e294880 RSI: ffffffff814e6de6 RDI: 0000000000000001
RBP: ffffc900008df750 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000004
R13: ffff888032d57c00 R14: 0000000000000000 R15: ffff88804583ef00
FS:  0000000000000000(0000) GS:ffff88806a900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd1e8385f98 CR3: 000000004b406000 CR4: 0000000000352ef0
DR0: 00000000e0002800 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 udp_queue_rcv_one_skb+0xad5/0x18c0 net/ipv4/udp.c:2135
 udp_queue_rcv_skb+0x198/0xd10 net/ipv4/udp.c:2213
 udp_unicast_rcv_skb+0x165/0x3b0 net/ipv4/udp.c:2373
 __udp4_lib_rcv+0x25fd/0x34e0 net/ipv4/udp.c:2449
 ip_protocol_deliver_rcu+0x2ff/0x4c0 net/ipv4/ip_input.c:205
 ip_local_deliver_finish+0x316/0x570 net/ipv4/ip_input.c:233
 NF_HOOK include/linux/netfilter.h:314 [inline]
 NF_HOOK include/linux/netfilter.h:308 [inline]
 ip_local_deliver+0x18e/0x1f0 net/ipv4/ip_input.c:254
 dst_input include/net/dst.h:460 [inline]
 ip_rcv_finish net/ipv4/ip_input.c:449 [inline]
 NF_HOOK include/linux/netfilter.h:314 [inline]
 NF_HOOK include/linux/netfilter.h:308 [inline]
 ip_rcv+0x2c3/0x5d0 net/ipv4/ip_input.c:569
 __netif_receive_skb_one_core+0x199/0x1e0 net/core/dev.c:5670
 __netif_receive_skb+0x1d/0x160 net/core/dev.c:5783
 process_backlog+0x443/0x15f0 net/core/dev.c:6115
 __napi_poll.constprop.0+0xb7/0x550 net/core/dev.c:6779
 napi_poll net/core/dev.c:6848 [inline]
 net_rx_action+0xa92/0x1010 net/core/dev.c:6970
 handle_softirqs+0x213/0x8f0 kernel/softirq.c:554
 run_ksoftirqd kernel/softirq.c:927 [inline]
 run_ksoftirqd+0x3a/0x60 kernel/softirq.c:919
 smpboot_thread_fn+0x661/0xa30 kernel/smpboot.c:164
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

             reply	other threads:[~2024-11-05  4:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  4:33 syzbot [this message]
2024-12-17 10:04 ` [syzbot] [net?] WARNING in geneve_udp_encap_recv 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=6729a011.050a0220.2edce.1501.GAE@google.com \
    --to=syzbot+c28dd30bc14158282b3b@syzkaller.appspotmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --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.