From: syzbot <syzbot+b68d24ad0de64bdba684@syzkaller.appspotmail.com>
To: glider@google.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] KMSAN: uninit-value in n_tty_receive_buf_common (2)
Date: Wed, 15 Dec 2021 00:54:22 -0800 [thread overview]
Message-ID: <000000000000c5543705d32b73bf@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 8b936c96768e kmsan: core: remove the accidentally committe..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=16469fc5b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e00a8959fdd3f3e8
dashboard link: https://syzkaller.appspot.com/bug?extid=b68d24ad0de64bdba684
compiler: clang version 14.0.0 (git@github.com:llvm/llvm-project.git 0996585c8e3b3d409494eb5f1cad714b9e1f7fb5), GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150a1e4db00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11c305bdb00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b68d24ad0de64bdba684@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in variable_test_bit arch/x86/include/asm/bitops.h:214 [inline]
BUG: KMSAN: uninit-value in test_bit include/asm-generic/bitops/instrumented-non-atomic.h:135 [inline]
BUG: KMSAN: uninit-value in n_tty_receive_buf_standard drivers/tty/n_tty.c:1557 [inline]
BUG: KMSAN: uninit-value in __receive_buf drivers/tty/n_tty.c:1577 [inline]
BUG: KMSAN: uninit-value in n_tty_receive_buf_common+0x1e6c/0x10360 drivers/tty/n_tty.c:1674
variable_test_bit arch/x86/include/asm/bitops.h:214 [inline]
test_bit include/asm-generic/bitops/instrumented-non-atomic.h:135 [inline]
n_tty_receive_buf_standard drivers/tty/n_tty.c:1557 [inline]
__receive_buf drivers/tty/n_tty.c:1577 [inline]
n_tty_receive_buf_common+0x1e6c/0x10360 drivers/tty/n_tty.c:1674
n_tty_receive_buf2+0xbe/0xd0 drivers/tty/n_tty.c:1709
tty_ldisc_receive_buf+0x15e/0x390 drivers/tty/tty_buffer.c:471
tty_port_default_receive_buf+0x14b/0x1e0 drivers/tty/tty_port.c:39
receive_buf drivers/tty/tty_buffer.c:491 [inline]
flush_to_ldisc+0x5bf/0xa10 drivers/tty/tty_buffer.c:543
process_one_work+0xdc2/0x1820 kernel/workqueue.c:2298
worker_thread+0x10f1/0x2290 kernel/workqueue.c:2445
kthread+0x721/0x850 kernel/kthread.c:327
ret_from_fork+0x1f/0x30
Uninit was created at:
slab_post_alloc_hook mm/slab.h:524 [inline]
slab_alloc_node mm/slub.c:3251 [inline]
slab_alloc mm/slub.c:3259 [inline]
__kmalloc+0xc3c/0x12d0 mm/slub.c:4437
kmalloc include/linux/slab.h:595 [inline]
tty_buffer_alloc drivers/tty/tty_buffer.c:177 [inline]
__tty_buffer_request_room+0x4d2/0x900 drivers/tty/tty_buffer.c:275
__tty_insert_flip_char+0xe5/0x3d0 drivers/tty/tty_buffer.c:392
tty_insert_flip_char include/linux/tty_flip.h:36 [inline]
uart_insert_char+0x495/0xb70 drivers/tty/serial/serial_core.c:3139
serial8250_read_char+0x280/0x820 drivers/tty/serial/8250/8250_port.c:1769
serial8250_rx_chars drivers/tty/serial/8250/8250_port.c:1784 [inline]
serial8250_handle_irq+0x540/0x980 drivers/tty/serial/8250/8250_port.c:1927
serial8250_default_handle_irq+0x18f/0x370 drivers/tty/serial/8250/8250_port.c:1949
serial8250_interrupt+0x111/0x3f0 drivers/tty/serial/8250/8250_core.c:126
__handle_irq_event_percpu+0x188/0xc90 kernel/irq/handle.c:158
handle_irq_event_percpu kernel/irq/handle.c:198 [inline]
handle_irq_event+0x188/0x420 kernel/irq/handle.c:215
handle_edge_irq+0x472/0x13e0 kernel/irq/chip.c:822
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq arch/x86/kernel/irq.c:231 [inline]
__common_interrupt+0xf8/0x360 arch/x86/kernel/irq.c:250
common_interrupt+0xb1/0xd0 arch/x86/kernel/irq.c:240
asm_common_interrupt+0x1e/0x40
CPU: 0 PID: 1056 Comm: kworker/u4:5 Not tainted 5.16.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2021-12-15 8:54 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=000000000000c5543705d32b73bf@google.com \
--to=syzbot+b68d24ad0de64bdba684@syzkaller.appspotmail.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--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 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.