Re: [PATCH] [v8]Input: evdev: fix bug of dropping valid packet after syn_dropped event

[Dmitry Torokhov]

Hi Anoroop,

On Thu, Jan 21, 2016 at 11:07:19PM +0530, Aniroop Mathur wrote:
> If last event dropped in the old queue was EVi_SYN/SYN_REPORT, then lets
> generate EV_SYN/SYN_REPORT immediately after queing EV_SYN/SYN_DROPPED
> so that clients would not ignore next valid full packet events.
> 
> Signed-off-by: Aniroop Mathur <a.mathur@xxxxxxxxxxx>
> ---
>  drivers/input/evdev.c | 46 ++++++++++++++++++++++++++++++++++------------
>  1 file changed, 34 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
> index e9ae3d5..821b68a 100644
> --- a/drivers/input/evdev.c
> +++ b/drivers/input/evdev.c
> @@ -156,7 +156,12 @@ static void __evdev_flush_queue(struct evdev_client *client, unsigned int type)
>  static void __evdev_queue_syn_dropped(struct evdev_client *client)
>  {
>  	struct input_event ev;
> +	struct input_event *last_ev;
>  	ktime_t time;
> +	unsigned int mask = client->bufsize - 1;
> +
> +	/* capture last event stored in the buffer */
> +	last_ev = &client->buffer[(client->head - 1) & mask];

I have still the same comment. How do you know that event at last_ev
position is in fact valid and unconsumed yet event. Also, you need to
figure out not only if queue contains last SYN event, but also to handle
the case where the queue is empty and client has consumed either full or
partial packet at the time you are queueing the drop.

Also please enumerate what changes you done between version n and n+1 so
I do not have to compare them line by line trying to figure it out
myself.

Thanks.

-- 
Dmitry