From: Dan Carpenter <dan.carpenter@linaro.org>
To: qasdev <qasdev00@gmail.com>
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] drivers/input: Fix null pointer dereferences in input_ff_create() and input_ff_create_memless()
Date: Thu, 9 Jan 2025 12:36:29 +0300 [thread overview]
Message-ID: <07395874-1434-476b-9bee-bcb786504ab0@stanley.mountain> (raw)
In-Reply-To: <Z36JJLAzwsFpggz2@qasdev.system>
On Wed, Jan 08, 2025 at 02:18:12PM +0000, qasdev wrote:
> Resending this patch as I have not received feedback since my initial submission on December 25, 2024.
> Please let me know if additional changes or information are required.
The bug isn't present in linux-next.
The original syzbot bug was already fixed in November last year. It
was fixed in a rebase so it doesn't exist in git history and I really
had to dig to understand what the issue was.
regards,
dan carpenter
prev parent reply other threads:[~2025-01-09 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 14:18 [PATCH RESEND] drivers/input: Fix null pointer dereferences in input_ff_create() and input_ff_create_memless() qasdev
2025-01-09 9:36 ` Dan Carpenter [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=07395874-1434-476b-9bee-bcb786504ab0@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qasdev00@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox