From: syzbot <syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [serial?] memory leak in gsm_activate_mux
Date: Mon, 06 Jul 2026 08:07:01 -0700 [thread overview]
Message-ID: <6a4bc495.b42ede87.8bd1.002b.GAE@google.com> (raw)
In-Reply-To: <1cea0f5e-32e1-4b01-b087-1e00f6fc976e@yandex.ru>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com
Tested-by: syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com
Tested on:
commit: 8cdeaa50 Linux 7.2-rc2
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=11783832580000
kernel config: https://syzkaller.appspot.com/x/.config?x=83d5b4d9fb5a5039
dashboard link: https://syzkaller.appspot.com/bug?extid=b5d1f455d385b2c7da3c
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=16e13546580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-07-06 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1cea0f5e-32e1-4b01-b087-1e00f6fc976e@yandex.ru>
2026-07-06 15:07 ` syzbot [this message]
[not found] <275ed678-5216-4d1c-bcff-22b63e689587@yandex.ru>
2026-07-06 13:55 ` [syzbot] [serial?] memory leak in gsm_activate_mux syzbot
2026-04-22 17:37 [PATCH] tty: n_gsm: fix " Minu Jin
2026-04-22 18:04 ` [syzbot] [serial?] " syzbot
-- strict thread matches above, loose matches on Subject: below --
2023-09-15 6:29 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=6a4bc495.b42ede87.8bd1.002b.GAE@google.com \
--to=syzbot+b5d1f455d385b2c7da3c@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 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.