[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024072930-badge-trilogy-c041@gregkh>
Date: Mon, 29 Jul 2024 16:28:38 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: Henrik Rydberg <rydberg@...math.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH (resend)] Input: MT - limit max slots
On Mon, Jul 29, 2024 at 10:15:26PM +0900, Tetsuo Handa wrote:
> On 2024/07/29 22:05, Greg Kroah-Hartman wrote:
> > On Mon, Jul 29, 2024 at 09:51:30PM +0900, Tetsuo Handa wrote:
> >> syzbot is reporting too large allocation at input_mt_init_slots(), for
> >> num_slots is supplied from userspace using ioctl(UI_DEV_CREATE).
> >>
> >> Since nobody knows possible max slots, this patch chose 1024.
> >>
> >> Reported-by: syzbot <syzbot+0122fa359a69694395d5@...kaller.appspotmail.com>
> >> Closes: https://syzkaller.appspot.com/bug?extid=0122fa359a69694395d5
> >> Suggested-by: Dmitry Torokhov <dmitry.torokhov@...il.com>
> >> Signed-off-by: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
> >> ---
> >> This patch was tested in linux-next between next-20240611 and next-20240729
> >> via my tree. Who can take this patch? If nobody can, I will send to Linus.
> >
> > What is wrong with the normal input maintainer and tree? Why not send
> > it there?
>
> I don't know why. I couldn't get further response from Dmitry Torokhov.
> Who can make final decision and what tree is used?
>
> e.g.
> 2022-11-23 0:28 https://lkml.kernel.org/r/03e8c3f0-bbbf-af37-6f52-67547cbd4cde@I-love.SAKURA.ne.jp
> 2023-09-03 13:55 https://lkml.kernel.org/r/07350163-de52-a2bf-58bf-88c3d9d8d85b@I-love.SAKURA.ne.jp
> 2024-05-27 10:35 https://lkml.kernel.org/r/7b7f9cf5-a1de-4e5a-8d30-bb2979309f02@I-love.SAKURA.ne.jp
>
Again, it's up to the Input maintainer.
Powered by blists - more mailing lists