From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
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: Mon, 29 Jul 2024 13:00:16 -0700 [thread overview]
Message-ID: <Zqf00C_eOBwcEiWG@google.com> (raw)
In-Reply-To: <CAHk-=wgo9iEZ20wB4rOpt6h36Dymudqf6HXww1N094bVoqyMmg@mail.gmail.com>
On Mon, Jul 29, 2024 at 12:27:05PM -0700, Linus Torvalds wrote:
> On Mon, 29 Jul 2024 at 12:12, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> >
> > OK, if you want to have limits be it. You probably want to lower from
> > 1024 to 128 or something, because with 1024 slots the structure will be
> > larger than one page and like I said mt->red table will be 4Mb.
>
> So this is why subsystem maintainers should be involved and helpful.
> It's hard to know what practical limits are.
>
> That said, a 4MB allocation for some test code is nothing.
>
> And yes, if syzbot hits other cases where the input layer just takes
> user input without any limit sanity checking, those should be fixed
> *too*.
Hmm, maybe the checks should go into drivers/input/misc/uinput.c which
is the only place that allows userspace to create input device instances
and drive them rather than into input core logic because all other
devices are backed by real hardware.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-07-29 20:00 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 [this message]
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
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=Zqf00C_eOBwcEiWG@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).