From: syzbot <syzbot+559c7fe4b8bac56d38c2@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, jirislaby@kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [serial?] KMSAN: uninit-value in n_tty_receive_buf_standard
Date: Mon, 01 Jan 2024 05:38:24 -0800 [thread overview]
Message-ID: <000000000000009d27060de27f0a@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 994d5c58e50e Merge tag 'hardening-v6.7-rc4' of git://git.k..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=15042a8ce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f711bc2a7eb1db25
dashboard link: https://syzkaller.appspot.com/bug?extid=559c7fe4b8bac56d38c2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1168e128e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14eebdaae80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ca8936129fcd/disk-994d5c58.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ce1c8de0e20b/vmlinux-994d5c58.xz
kernel image: https://storage.googleapis.com/syzbot-assets/89ceb1dd4d79/bzImage-994d5c58.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+559c7fe4b8bac56d38c2@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in variable_test_bit arch/x86/include/asm/bitops.h:227 [inline]
BUG: KMSAN: uninit-value in arch_test_bit arch/x86/include/asm/bitops.h:239 [inline]
BUG: KMSAN: uninit-value in _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]
BUG: KMSAN: uninit-value in n_tty_receive_buf_standard+0xc58/0x9230 drivers/tty/n_tty.c:1603
variable_test_bit arch/x86/include/asm/bitops.h:227 [inline]
arch_test_bit arch/x86/include/asm/bitops.h:239 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:142 [inline]
n_tty_receive_buf_standard+0xc58/0x9230 drivers/tty/n_tty.c:1603
__receive_buf drivers/tty/n_tty.c:1630 [inline]
n_tty_receive_buf_common+0x178e/0x2310 drivers/tty/n_tty.c:1729
n_tty_receive_buf2+0x4c/0x60 drivers/tty/n_tty.c:1775
tty_ldisc_receive_buf+0xce/0x270 drivers/tty/tty_buffer.c:386
tty_port_default_receive_buf+0xdf/0x190 drivers/tty/tty_port.c:37
receive_buf drivers/tty/tty_buffer.c:444 [inline]
flush_to_ldisc+0x4b7/0xdc0 drivers/tty/tty_buffer.c:494
process_one_work kernel/workqueue.c:2630 [inline]
process_scheduled_works+0x104e/0x1e70 kernel/workqueue.c:2703
worker_thread+0xf45/0x1490 kernel/workqueue.c:2784
kthread+0x3ed/0x540 kernel/kthread.c:388
ret_from_fork+0x66/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
Uninit was created at:
slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768
slab_alloc_node mm/slub.c:3478 [inline]
__kmem_cache_alloc_node+0x5c9/0x970 mm/slub.c:3517
__do_kmalloc_node mm/slab_common.c:1006 [inline]
__kmalloc+0x121/0x3c0 mm/slab_common.c:1020
kmalloc include/linux/slab.h:604 [inline]
tty_buffer_alloc drivers/tty/tty_buffer.c:179 [inline]
__tty_buffer_request_room+0x36e/0x6c0 drivers/tty/tty_buffer.c:272
__tty_insert_flip_string_flags+0x140/0x560 drivers/tty/tty_buffer.c:308
tty_insert_flip_char include/linux/tty_flip.h:77 [inline]
uart_insert_char+0x39e/0xa00 drivers/tty/serial/serial_core.c:3494
serial8250_read_char+0x1a2/0x5d0 drivers/tty/serial/8250/8250_port.c:1760
serial8250_rx_chars drivers/tty/serial/8250/8250_port.c:1777 [inline]
serial8250_handle_irq+0x77b/0xb30 drivers/tty/serial/8250/8250_port.c:1937
serial8250_default_handle_irq+0x11a/0x2a0 drivers/tty/serial/8250/8250_port.c:1962
serial8250_interrupt+0xc0/0x350 drivers/tty/serial/8250/8250_core.c:127
__handle_irq_event_percpu+0x113/0xc90 kernel/irq/handle.c:158
handle_irq_event_percpu kernel/irq/handle.c:193 [inline]
handle_irq_event+0xef/0x2c0 kernel/irq/handle.c:210
handle_edge_irq+0x341/0xf90 kernel/irq/chip.c:831
generic_handle_irq_desc include/linux/irqdesc.h:161 [inline]
handle_irq arch/x86/kernel/irq.c:238 [inline]
__common_interrupt+0x94/0x1f0 arch/x86/kernel/irq.c:257
common_interrupt+0x89/0xa0 arch/x86/kernel/irq.c:247
asm_common_interrupt+0x2b/0x40 arch/x86/include/asm/idtentry.h:636
CPU: 0 PID: 3894 Comm: kworker/u4:23 Not tainted 6.7.0-rc3-syzkaller-00134-g994d5c58e50e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Workqueue: events_unbound flush_to_ldisc
=====================================================
---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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-01-01 13:38 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=000000000000009d27060de27f0a@google.com \
--to=syzbot+559c7fe4b8bac56d38c2@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 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.