mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+a81f2759d022496b40ab@syzkaller.appspotmail.com>
To: aha310510@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KMSAN: uninit-value in hsr_get_node (3)
Date: Fri, 19 Jul 2024 17:38:02 -0700	[thread overview]
Message-ID: <0000000000004e613b061da30600@google.com> (raw)
In-Reply-To: <20240719162238.71387-1-aha310510@gmail.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in hsr_get_node

=====================================================
BUG: KMSAN: uninit-value in hsr_get_node+0xd05/0xd30 net/hsr/hsr_framereg.c:275
 hsr_get_node+0xd05/0xd30 net/hsr/hsr_framereg.c:275
 fill_frame_info net/hsr/hsr_forward.c:678 [inline]
 hsr_forward_skb+0xe9d/0x3b40 net/hsr/hsr_forward.c:715
 hsr_handle_frame+0x914/0xbb0 net/hsr/hsr_slave.c:70
 __netif_receive_skb_core+0x1f19/0x6c90 net/core/dev.c:5554
 __netif_receive_skb_one_core net/core/dev.c:5658 [inline]
 __netif_receive_skb+0xca/0xa00 net/core/dev.c:5774
 netif_receive_skb_internal net/core/dev.c:5860 [inline]
 netif_receive_skb+0x58/0x660 net/core/dev.c:5920
 tun_rx_batched+0x3ee/0x980 drivers/net/tun.c:1549
 tun_get_user+0x5677/0x6b50 drivers/net/tun.c:2006
 tun_chr_write_iter+0x3af/0x5d0 drivers/net/tun.c:2052
 new_sync_write fs/read_write.c:497 [inline]
 vfs_write+0xb2f/0x1550 fs/read_write.c:590
 ksys_write+0x20f/0x4c0 fs/read_write.c:643
 __do_sys_write fs/read_write.c:655 [inline]
 __se_sys_write fs/read_write.c:652 [inline]
 __x64_sys_write+0x93/0xe0 fs/read_write.c:652
 x64_sys_call+0x3490/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:2
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Uninit was created at:
 __alloc_pages_noprof+0x9d6/0xe70 mm/page_alloc.c:4706
 alloc_pages_mpol_noprof+0x299/0x990 mm/mempolicy.c:2265
 alloc_pages_noprof+0x1bf/0x1e0 mm/mempolicy.c:2336
 skb_page_frag_refill+0x2bf/0x7c0 net/core/sock.c:2941
 tun_build_skb drivers/net/tun.c:1680 [inline]
 tun_get_user+0x1262/0x6b50 drivers/net/tun.c:1823
 tun_chr_write_iter+0x3af/0x5d0 drivers/net/tun.c:2052
 new_sync_write fs/read_write.c:497 [inline]
 vfs_write+0xb2f/0x1550 fs/read_write.c:590
 ksys_write+0x20f/0x4c0 fs/read_write.c:643
 __do_sys_write fs/read_write.c:655 [inline]
 __se_sys_write fs/read_write.c:652 [inline]
 __x64_sys_write+0x93/0xe0 fs/read_write.c:652
 x64_sys_call+0x3490/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:2
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

CPU: 0 PID: 5480 Comm: syz-executor.0 Not tainted 6.10.0-syzkaller-09703-gd7e78951a8b8-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
=====================================================


Tested on:

commit:         d7e78951 Merge tag 'net-6.11-rc0' of git://git.kernel...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=116a2349980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=be93d3b0d4dc66d7
dashboard link: https://syzkaller.appspot.com/bug?extid=a81f2759d022496b40ab
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=106b443d980000


  reply	other threads:[~2024-07-20  0:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  4:08 syzbot
2024-04-18  8:40 ` Jeongjun Park
2024-04-18 17:39   ` syzbot
2024-04-19 13:03 ` Jeongjun Park
2024-04-19 15:12   ` syzbot
2024-04-19 15:51 ` Jeongjun Park
2024-04-19 16:45   ` syzbot
2024-07-17 14:51 ` Jeongjun Park
2024-07-17 16:36   ` syzbot
2024-07-18 12:04 ` Jeongjun Park
2024-07-18 12:29   ` syzbot
2024-07-18 12:34 ` Jeongjun Park
2024-07-18 13:04   ` syzbot
2024-07-18 23:24 ` Jeongjun Park
2024-07-19  3:07   ` syzbot
2024-07-19 16:22 ` Jeongjun Park
2024-07-20  0:38   ` syzbot [this message]
2024-07-20  8:18 ` [syzbot] " syzbot
2024-07-20  8:30 ` syzbot
2024-07-20 10:53 ` syzbot
2025-08-20 16:45 ` Forwarded: Test for a81f2759d022496b40ab syzbot
     [not found] <20240720081802.79749-1-aha310510@gmail.com>
2024-07-20  8:45 ` [syzbot] [net?] KMSAN: uninit-value in hsr_get_node (3) syzbot
     [not found] <20240720083036.80392-1-aha310510@gmail.com>
2024-07-20  9:05 ` syzbot
     [not found] <20240720105318.114879-1-aha310510@gmail.com>
2024-07-20 11:22 ` syzbot
     [not found] <aKX7nTwVVk9dVAkn@kernel-devel>
2025-08-20 17:25 ` 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=0000000000004e613b061da30600@google.com \
    --to=syzbot+a81f2759d022496b40ab@syzkaller.appspotmail.com \
    --cc=aha310510@gmail.com \
    --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