From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: 许东洁 <xudongjie25@mails.ucas.ac.cn>
Cc: linux-input@vger.kernel.org, zhaoruilin22@mails.ucas.ac.cn
Subject: Re: [BUG] list_add double add in cm109_input_open
Date: Tue, 14 Apr 2026 21:03:02 -0700 [thread overview]
Message-ID: <ad8M-FjZie-QVJNB@google.com> (raw)
In-Reply-To: <1fdc2218.4cc75.19d8f37b6dd.Coremail.xudongjie25@mails.ucas.ac.cn>
On Wed, Apr 15, 2026 at 11:38:06AM +0800, 许东洁 wrote:
> Hi,
>
> While running fuzzing tests on 6.19.0-rc5, we hit a "list_add double add" bug triggered by the cm109 driver.
>
> The root cause lies in how the driver handles multiple input devices. During probe, the driver registers two separate input devices (idev and keypad). Both devices share the same cm109_input_open() and cm109_input_close() callbacks. If both input devices are opened by user space, cm109_input_open() is called twice.
Your LLM hallucinated a bunch of stuff. Please refrain from reporting
any more "bugs" to us.
Thanks.
--
Dmitry
prev parent reply other threads:[~2026-04-15 4:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 3:38 [BUG] list_add double add in cm109_input_open 许东洁
2026-04-15 4:03 ` Dmitry Torokhov [this message]
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=ad8M-FjZie-QVJNB@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=xudongjie25@mails.ucas.ac.cn \
--cc=zhaoruilin22@mails.ucas.ac.cn \
/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