From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Henrik Rydberg <rydberg@bitmath.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH (resend)] Input: MT - limit max slots
Date: Tue, 30 Jul 2024 14:52:01 -0700 [thread overview]
Message-ID: <ZqlggV3G0t743exX@google.com> (raw)
In-Reply-To: <3ace9a7f-159f-4c61-807a-c0d9be996986@I-love.SAKURA.ne.jp>
Hi Tetsuo,
On Tue, Jul 30, 2024 at 02:38:19PM +0900, Tetsuo Handa wrote:
> On 2024/07/30 2:59, Dmitry Torokhov wrote:
> > Please do not. Or you will have to patch it again when we will still see
> > the same allocation failures because someone requested an input device
> > with "too many" slots (1024 results in 4Mb mt->red table for example).
> >
> > Just fix malloc/syzkaller not to trigger on benign memory allocation
> > hickups. They are normal.
>
> I chose 1024 because as far as I know 4MB is max acceptable size for
> all environments without triggering too large allocation warning.
>
> You worry about mt->red, but did you notice that syzbot was reporting that
> memory allocation for mt->red has an integer overflow bug, which can cause
> out of bounds write or ZERO_SIZE_PTR pointer dereference bug at input_mt_set_matrix() ?
>
> https://lkml.kernel.org/r/6d878e01-6c2f-8766-2578-c95030442369@I-love.SAKURA.ne.jp
I'll happily take the change converting that to array_size().
>
> Lucky thing is that the uinput interface is for only the "root" user...
uinput also does not request in-kernel contact tracking so it will not
allow hitting that overflow.
Thanks.
--
Dmitry
prev parent reply other threads:[~2024-07-30 21:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 12:51 [PATCH (resend)] Input: MT - limit max slots Tetsuo Handa
2024-07-29 13:05 ` Greg Kroah-Hartman
2024-07-29 13:15 ` Tetsuo Handa
2024-07-29 14:28 ` Greg Kroah-Hartman
2024-07-29 15:57 ` Dmitry Torokhov
2024-07-29 17:43 ` Linus Torvalds
2024-07-29 17:59 ` Dmitry Torokhov
2024-07-29 18:16 ` Linus Torvalds
2024-07-29 18:35 ` Dmitry Torokhov
2024-07-29 18:41 ` Linus Torvalds
2024-07-29 19:12 ` Dmitry Torokhov
2024-07-29 19:27 ` Linus Torvalds
2024-07-29 20:00 ` Dmitry Torokhov
2024-07-29 20:14 ` Linus Torvalds
2024-07-29 23:17 ` Dmitry Torokhov
2024-07-30 5:38 ` Tetsuo Handa
2024-07-30 21:52 ` 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=ZqlggV3G0t743exX@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rydberg@bitmath.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).