linux-kernel - Re: [PATCH] Input: evdev - add ioctl cmd EVIOCGBUFSIZE to get buffer size

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 8 Jan 2016 20:33:40 +0000
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Aniroop Mathur <aniroop.mathur@...il.com>
Cc:	David Herrmann <dh.herrmann@...il.com>,
	Aniroop Mathur <a.mathur@...sung.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	"open list:HID CORE LAYER" <linux-input@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Input: evdev - add ioctl cmd EVIOCGBUFSIZE to get
 buffer size

On Sat, 9 Jan 2016 01:50:42 +0530
Aniroop Mathur <aniroop.mathur@...il.com> wrote:

> On Sat, Jan 9, 2016 at 1:43 AM, One Thousand Gnomes
> <gnomes@...rguk.ukuu.org.uk> wrote:
> >> During system boot up, user space buf size is fixed, it cannot be
> >> resized later and we cannot choose by hit&trial.
> >> struct input_event* mBuffer = new input_event[mBuf];
> >
> > Who says that won't change ? Imagine a future case where plugging in a
> > device changes the buffer size ?
> >
> 
> Ofcourse buffer size can be changed but it will also change the value of bufsize
> variable and accordingly user space client should also change its buf size.

If its hot plugged why shouldn't that value change dynamically after
you've asked ?

Alan