mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+4d55dad3a9e8e9f7d2b5@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KASAN: use-after-free Read in __ocfs2_flush_truncate_log
Date: Wed, 29 Oct 2025 01:02:03 -0700	[thread overview]
Message-ID: <6901c9fb.050a0220.3344a1.0414.GAE@google.com> (raw)
In-Reply-To: <20251029062151.Gq0gL%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

IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
================================================================================
UBSAN: signed-integer-overflow in ./arch/x86/include/asm/atomic.h:165:11
360654889 + 1871359415 cannot be represented in type 'int'
CPU: 1 PID: 128 Comm: kworker/u4:3 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
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+0x465/0x840 net/ipv4/ip_tunnel_core.c:80
 udp_tunnel_xmit_skb+0x1b7/0x280 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+0x85b/0xfe0 kernel/workqueue.c:2282
 worker_thread+0xa9b/0x1430 kernel/workqueue.c:2428
 kthread+0x384/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: 1 PID: 128 Comm: kworker/u4:3 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
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+0x465/0x840 net/ipv4/ip_tunnel_core.c:80
 udp_tunnel_xmit_skb+0x1b7/0x280 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+0x85b/0xfe0 kernel/workqueue.c:2282
 worker_thread+0xa9b/0x1430 kernel/workqueue.c:2428
 kthread+0x384/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=10759f34580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=bf23b541eb2e03cb
dashboard link: https://syzkaller.appspot.com/bug?extid=4d55dad3a9e8e9f7d2b5
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=12983e7c580000


       reply	other threads:[~2025-10-29  8:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251029062151.Gq0gL%dmantipov@yandex.ru>
2025-10-29  8:02 ` syzbot [this message]
     [not found] <20251029062739.WT_1W%dmantipov@yandex.ru>
2025-10-29 15:25 ` syzbot
     [not found] <20251029062544.q4Amh%dmantipov@yandex.ru>
2025-10-29 12:43 ` syzbot
     [not found] <20251028182247.yvNrt%dmantipov@yandex.ru>
2025-10-28 21:28 ` syzbot
     [not found] <20251028182010.VCEv_%dmantipov@yandex.ru>
2025-10-28 20:43 ` syzbot
     [not found] <20251028181930.boW79%dmantipov@yandex.ru>
2025-10-28 18:27 ` syzbot
     [not found] <20251028104156.MqXWB%dmantipov@yandex.ru>
2025-10-28 10:47 ` syzbot
     [not found] <20251028104117.Q0izB%dmantipov@yandex.ru>
2025-10-28 10:45 ` syzbot
     [not found] <20251028104003.OE-Gy%dmantipov@yandex.ru>
2025-10-28 10:41 ` syzbot
     [not found] <20251024071530.lavdB%dmantipov@yandex.ru>
2025-10-24 13:39 ` syzbot
     [not found] <20251024071518.x1MIZ%dmantipov@yandex.ru>
2025-10-24 12:20 ` syzbot
     [not found] <20251024071151.6PBhO%dmantipov@yandex.ru>
2025-10-24  7:48 ` syzbot
     [not found] <20251022121354.-oB1f%dmantipov@yandex.ru>
2025-10-22 13:01 ` syzbot
     [not found] <068e55cc-f5c0-42ad-99b5-352830583144@yandex.ru>
2025-10-22 10:50 ` syzbot
     [not found] <a9cfa569-b234-4ad0-b2e5-1a227e7ea9ac@yandex.ru>
2025-10-20 11:11 ` syzbot
     [not found] <cbd65371-547c-4644-9e68-9958e348e9ec@yandex.ru>
2025-10-20 10:50 ` syzbot
2024-09-29  4:47 Lizhi Xu
2024-09-29  5:09 ` [syzbot] " syzbot
  -- strict thread matches above, loose matches on Subject: below --
2024-09-28 20:44 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=6901c9fb.050a0220.3344a1.0414.GAE@google.com \
    --to=syzbot+4d55dad3a9e8e9f7d2b5@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

Powered by JetHome