From: Dan Carpenter <dan.carpenter@linaro.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Dongliang Mu <dzm91@hust.edu.cn>, Vicki Pfau <vi@endrift.com>,
kernel-janitors@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Pavel Rojtberg <rojtberg@gmail.com>, Nate Yocom <nate@yocom.org>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
John Butler <radon86dev@gmail.com>,
Matthias Benkmann <matthias.benkmann@gmail.com>,
Christopher Crockett <chaorace@gmail.com>,
Santosh De Massari <s.demassari@gmail.com>,
hust-os-kernel-patches@googlegroups.com,
syzbot+a3f758b8d8cb7e49afec@syzkaller.appspotmail.com,
"Pierre-Loup A. Griffais" <pgriffais@valvesoftware.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: xpad - fix GPF in xpad_probe
Date: Sat, 22 Apr 2023 22:56:39 +0300 [thread overview]
Message-ID: <c12873b2-d2e5-4fbc-987f-fa96cbe926da@kili.mountain> (raw)
In-Reply-To: <d49bb5a2-ed78-4b16-b7ea-b9c7748ca0e4@kili.mountain>
On Sat, Apr 22, 2023 at 10:48:32PM +0300, Dan Carpenter wrote:
> The warnings from this are quite promising.
Well... The results are over 90% false positives. But there are still
probably 15 bugs in there. The printk warning trick would probably
work.
regards,
dan carpenter
next prev parent reply other threads:[~2023-04-22 19:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 12:55 [PATCH] Input: xpad - fix GPF in xpad_probe Dongliang Mu
2023-04-17 9:25 ` Dan Carpenter
[not found] ` <99794af0-7367-acff-357d-1cd4fa7f832e@hust.edu.cn>
2023-04-17 10:24 ` Vicki Pfau
[not found] ` <57577302-8d18-231f-062b-b1d262720943@hust.edu.cn>
2023-04-17 11:07 ` Vicki Pfau
2023-04-17 11:15 ` Dongliang Mu
2023-04-17 10:42 ` Dan Carpenter
2023-04-20 11:07 ` Dan Carpenter
2023-04-22 19:48 ` Dan Carpenter
2023-04-22 19:56 ` Dan Carpenter [this message]
2023-04-23 2:33 ` Dongliang Mu
2023-05-02 10:34 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 21:12 Claudia De-Massari
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=c12873b2-d2e5-4fbc-987f-fa96cbe926da@kili.mountain \
--to=dan.carpenter@linaro.org \
--cc=chaorace@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=error27@gmail.com \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.benkmann@gmail.com \
--cc=mkorpershoek@baylibre.com \
--cc=nate@yocom.org \
--cc=pgriffais@valvesoftware.com \
--cc=radon86dev@gmail.com \
--cc=rojtberg@gmail.com \
--cc=s.demassari@gmail.com \
--cc=syzbot+a3f758b8d8cb7e49afec@syzkaller.appspotmail.com \
--cc=vi@endrift.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