Re: [PATCH 2/9] input: Fix possible crash in clip_pointer_motion

2013-05-29 Thread Kristian Høgsberg
On Wed, May 29, 2013 at 09:25:33AM +0200, Alexander Larsson wrote: > On tis, 2013-05-28 at 17:25 -0400, Kristian Høgsberg wrote: > > On Tue, May 28, 2013 at 04:23:33PM +0200, al...@redhat.com wrote: > > > From: Alexander Larsson > > > > > > It was erronously using output->current->height in one >

Re: [PATCH 2/9] input: Fix possible crash in clip_pointer_motion

2013-05-29 Thread Alexander Larsson
On tis, 2013-05-28 at 17:25 -0400, Kristian Høgsberg wrote: > On Tue, May 28, 2013 at 04:23:33PM +0200, al...@redhat.com wrote: > > From: Alexander Larsson > > > > It was erronously using output->current->height in one > > place where it should use output->height. This may cause > > it to create

Re: [PATCH 2/9] input: Fix possible crash in clip_pointer_motion

2013-05-28 Thread Kristian Høgsberg
On Tue, May 28, 2013 at 04:23:33PM +0200, al...@redhat.com wrote: > From: Alexander Larsson > > It was erronously using output->current->height in one > place where it should use output->height. This may cause > it to create an invalid clipped coordinate in case of output > scaling or transform,

[PATCH 2/9] input: Fix possible crash in clip_pointer_motion

2013-05-28 Thread alexl
From: Alexander Larsson It was erronously using output->current->height in one place where it should use output->height. This may cause it to create an invalid clipped coordinate in case of output scaling or transform, because the next round "prev" would end up NULL. --- src/input.c | 2 +- 1 fi