All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+dd514b5f0cf048aec256@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: KMSAN: uninit-value in n_tty_receive_buf_closing (3)
Date: Wed, 24 Sep 2025 22:40:42 -0700	[thread overview]
Message-ID: <68d4d5da.050a0220.3a612a.0001.GAE@google.com> (raw)
In-Reply-To: <0000000000000a1b9a0620097bad@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: KMSAN: uninit-value in n_tty_receive_buf_closing (3)
Author: rampxxxx@gmail.com

#syz test

---

diff --git a/drivers/tty/tty_buffer.c b/drivers/tty/tty_buffer.c
index 79f0ff94ce00..b297e3fafdf7 100644
--- a/drivers/tty/tty_buffer.c
+++ b/drivers/tty/tty_buffer.c
@@ -177,7 +177,7 @@ static struct tty_buffer *tty_buffer_alloc(struct
tty_port *port, size_t size)
        */
       if (atomic_read(&port->buf.mem_used) > port->buf.mem_limit)
               return NULL;
-       p = kmalloc(struct_size(p, data, 2 * size), GFP_ATOMIC | __GFP_NOWARN);
+       p = kzalloc(struct_size(p, data, 2 * size), GFP_ATOMIC | __GFP_NOWARN);
       if (p == NULL)
               return NULL;

  parent reply	other threads:[~2025-09-25  5:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19 13:42 [syzbot] [serial?] KMSAN: uninit-value in n_tty_receive_buf_closing (3) syzbot
2024-12-27 18:44 ` syzbot
2025-09-25  5:40 ` syzbot [this message]
     [not found] <20250925062317.1281522-1-kartikey406@gmail.com>
2025-09-25  7:02 ` [syzbot] [fs?] [mm?] WARNING: bad unlock balance in hugetlb_vmdelete_list syzbot
2025-09-25  8:41   ` [PATCH] KMSAN: uninit-value in n_tty_receive_buf_closing Pei Xiao
2025-09-25  8:52     ` Pei Xiao
2025-09-25  8:47     ` Pei Xiao
2025-09-25  9:05     ` [syzbot] [fs?] [mm?] WARNING: bad unlock balance in hugetlb_vmdelete_list syzbot
2025-09-25 10:09     ` [syzbot] [serial?] KMSAN: uninit-value in n_tty_receive_buf_closing (3) 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=68d4d5da.050a0220.3a612a.0001.GAE@google.com \
    --to=syzbot+dd514b5f0cf048aec256@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.