From: syzbot <syzbot+727d161855d11d81e411@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] kernel BUG in __ocfs2_move_extent
Date: Fri, 24 Oct 2025 00:32:02 -0700 [thread overview]
Message-ID: <68fb2b72.050a0220.346f24.00ac.GAE@google.com> (raw)
In-Reply-To: <20251024071152.RMTIq%dmantipov@yandex.ru>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
UBSAN: signed-integer-overflow in ip_idents_reserve
================================================================================
UBSAN: signed-integer-overflow in ./arch/x86/include/asm/atomic.h:165:11
-481196967 + -1672998446 cannot be represented in type 'int'
CPU: 0 PID: 3019 Comm: kworker/u2:4 Not tainted syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: wg-kex-wg0 wg_packet_handshake_send_worker
Call Trace:
dump_stack+0xfd/0x16e lib/dump_stack.c:118
ubsan_epilogue+0xa/0x30 lib/ubsan.c:148
handle_overflow+0x192/0x1b0 lib/ubsan.c:180
arch_atomic_add_return arch/x86/include/asm/atomic.h:165 [inline]
atomic_add_return include/asm-generic/atomic-instrumented.h:73 [inline]
ip_idents_reserve+0x14a/0x170 net/ipv4/route.c:521
__ip_select_ident+0xe4/0x1c0 net/ipv4/route.c:538
iptunnel_xmit+0x468/0x850 net/ipv4/ip_tunnel_core.c:80
udp_tunnel_xmit_skb+0x1ba/0x290 net/ipv4/udp_tunnel_core.c:190
send4+0x5d4/0xaf0 drivers/net/wireguard/socket.c:85
wg_socket_send_skb_to_peer+0xcd/0x1c0 drivers/net/wireguard/socket.c:175
wg_packet_send_handshake_initiation drivers/net/wireguard/send.c:40 [inline]
wg_packet_handshake_send_worker+0x16b/0x280 drivers/net/wireguard/send.c:51
process_one_work+0x85e/0xff0 kernel/workqueue.c:2282
worker_thread+0xa9b/0x1430 kernel/workqueue.c:2428
kthread+0x386/0x410 kernel/kthread.c:328
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
================================================================================
Kernel panic - not syncing: UBSAN: panic_on_warn set ...
CPU: 0 PID: 3019 Comm: kworker/u2:4 Not tainted syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: wg-kex-wg0 wg_packet_handshake_send_worker
Call Trace:
dump_stack+0xfd/0x16e lib/dump_stack.c:118
panic+0x2f0/0x9c0 kernel/panic.c:308
check_panic_on_warn+0x95/0xe0 kernel/panic.c:228
handle_overflow+0x192/0x1b0 lib/ubsan.c:180
arch_atomic_add_return arch/x86/include/asm/atomic.h:165 [inline]
atomic_add_return include/asm-generic/atomic-instrumented.h:73 [inline]
ip_idents_reserve+0x14a/0x170 net/ipv4/route.c:521
__ip_select_ident+0xe4/0x1c0 net/ipv4/route.c:538
iptunnel_xmit+0x468/0x850 net/ipv4/ip_tunnel_core.c:80
udp_tunnel_xmit_skb+0x1ba/0x290 net/ipv4/udp_tunnel_core.c:190
send4+0x5d4/0xaf0 drivers/net/wireguard/socket.c:85
wg_socket_send_skb_to_peer+0xcd/0x1c0 drivers/net/wireguard/socket.c:175
wg_packet_send_handshake_initiation drivers/net/wireguard/send.c:40 [inline]
wg_packet_handshake_send_worker+0x16b/0x280 drivers/net/wireguard/send.c:51
process_one_work+0x85e/0xff0 kernel/workqueue.c:2282
worker_thread+0xa9b/0x1430 kernel/workqueue.c:2428
kthread+0x386/0x410 kernel/kthread.c:328
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
Kernel Offset: disabled
Rebooting in 86400 seconds..
Tested on:
commit: d3d0b4e2 Linux 5.10.245
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git linux-5.10.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17aeae7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=26c538ce4091baa9
dashboard link: https://syzkaller.appspot.com/bug?extid=727d161855d11d81e411
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=16369be2580000
next parent reply other threads:[~2025-10-24 7:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251024071152.RMTIq%dmantipov@yandex.ru>
2025-10-24 7:32 ` syzbot [this message]
[not found] <20251029062741.TtsCS%dmantipov@yandex.ru>
2025-10-29 9:19 ` [syzbot] [ocfs2?] kernel BUG in __ocfs2_move_extent syzbot
[not found] <20251029062547.rwhxA%dmantipov@yandex.ru>
2025-10-29 7:45 ` syzbot
[not found] <20251029062152.SGmfc%dmantipov@yandex.ru>
2025-10-29 6:41 ` syzbot
[not found] <20251028182251.0GoZ4%dmantipov@yandex.ru>
2025-10-28 19:51 ` syzbot
[not found] <20251028182057.zO55R%dmantipov@yandex.ru>
2025-10-28 18:59 ` syzbot
[not found] <20251028181934.eY2E6%dmantipov@yandex.ru>
2025-10-28 18:33 ` syzbot
[not found] <20251028104158.MIVL6%dmantipov@yandex.ru>
2025-10-28 10:45 ` syzbot
[not found] <20251028104119.GRrZG%dmantipov@yandex.ru>
2025-10-28 10:43 ` syzbot
[not found] <20251028104005.KTUK2%dmantipov@yandex.ru>
2025-10-28 10:42 ` syzbot
[not found] <20251024071531.Cp40p%dmantipov@yandex.ru>
2025-10-24 9:51 ` syzbot
[not found] <20251024071520.3EwpH%dmantipov@yandex.ru>
2025-10-24 8:39 ` syzbot
[not found] <20251022121135.b09g-%dmantipov@yandex.ru>
2025-10-22 12:35 ` syzbot
[not found] <fbb0d602-f99c-44b8-a0a1-9d6ab5b3c107@yandex.ru>
2025-10-08 11:13 ` syzbot
2025-10-07 3:55 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=68fb2b72.050a0220.346f24.00ac.GAE@google.com \
--to=syzbot+727d161855d11d81e411@syzkaller.appspotmail.com \
--cc=dmantipov@yandex.ru \
--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