Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-30 Thread Dan Carpenter
On Wed, Nov 30, 2016 at 03:53:03PM +0200, Laurent Pinchart wrote: > But then you get the following patch (which, apart from being totally made > up, > probably shows what I've watched yesterday evening). > > @@ ... @@ > return -ENOMEM; > } > > + ret = check_time_vortex(

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-30 Thread Laurent Pinchart
Hi Dan, On Wednesday 30 Nov 2016 15:33:26 Dan Carpenter wrote: > On Mon, Nov 28, 2016 at 04:49:36PM +0200, Laurent Pinchart wrote: > > On Monday 28 Nov 2016 14:54:58 Julia Lawall wrote: > >> On Mon, 28 Nov 2016, Dan Carpenter wrote: > >>> I understand the comparison, but I just think it's better i

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-30 Thread Dan Carpenter
On Mon, Nov 28, 2016 at 04:49:36PM +0200, Laurent Pinchart wrote: > Hi Julia and Dan, > > On Monday 28 Nov 2016 14:54:58 Julia Lawall wrote: > > On Mon, 28 Nov 2016, Dan Carpenter wrote: > > > I understand the comparison, but I just think it's better if people > > > always keep track of what has b

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-28 Thread Julia Lawall
To put it another way, tools can figure out what is missing if they have access to good exmples of what should be there. To be clear, I can see both points of view. julia -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.or

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-28 Thread Laurent Pinchart
Hi Julia and Dan, On Monday 28 Nov 2016 14:54:58 Julia Lawall wrote: > On Mon, 28 Nov 2016, Dan Carpenter wrote: > > I understand the comparison, but I just think it's better if people > > always keep track of what has been allocated and what has not. I tried > > so hard to get Markus to stop sen

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-28 Thread Julia Lawall
On Mon, 28 Nov 2016, Dan Carpenter wrote: > I understand the comparison, but I just think it's better if people > always keep track of what has been allocated and what has not. I tried > so hard to get Markus to stop sending those hundreds of patches where > he's like "this function has a sanit

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-28 Thread Dan Carpenter
I understand the comparison, but I just think it's better if people always keep track of what has been allocated and what has not. I tried so hard to get Markus to stop sending those hundreds of patches where he's like "this function has a sanity check so we can pass pointers that weren't allocate

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-27 Thread Sakari Alius
Hi Dan, On Fri, Nov 25, 2016 at 10:20:24PM +0300, Dan Carpenter wrote: > On Fri, Nov 25, 2016 at 06:02:45PM +0200, Laurent Pinchart wrote: > > Sakari Ailus (CC'ed) has expressed the opinion that we might want to go one > > step further and treat error pointers the same way we treat NULL or ZERO

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-25 Thread Dan Carpenter
On Fri, Nov 25, 2016 at 06:02:45PM +0200, Laurent Pinchart wrote: > Sakari Ailus (CC'ed) has expressed the opinion that we might want to go one > step further and treat error pointers the same way we treat NULL or ZERO > pointers today, by just returning without logging anything. The reasoning is

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-25 Thread Dan Carpenter
On Fri, Nov 25, 2016 at 03:57:51PM +0200, Laurent Pinchart wrote: > diff --git a/mm/slab.c b/mm/slab.c > index 0b0550ca85b4..a7eb830c6684 100644 > --- a/mm/slab.c > +++ b/mm/slab.c > @@ -3819,6 +3819,8 @@ void kfree(const void *objp) > > if (unlikely(ZERO_OR_NULL_PTR(objp))) >

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-25 Thread Laurent Pinchart
Hi Walter, On Friday 25 Nov 2016 15:47:49 walter harms wrote: > Am 25.11.2016 14:57, schrieb Laurent Pinchart: > > On Friday 25 Nov 2016 13:28:35 Dan Carpenter wrote: > >> A recent cleanup introduced a potential dereference of -EFAULT when we > >> call kfree(map->menu_info). > > > > I should have

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-25 Thread walter harms
Am 25.11.2016 14:57, schrieb Laurent Pinchart: > Hi Dan, > > Thank you for the patch. > > On Friday 25 Nov 2016 13:28:35 Dan Carpenter wrote: >> A recent cleanup introduced a potential dereference of -EFAULT when we >> call kfree(map->menu_info). > > I should have caught that, my apologies :-(

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-25 Thread Laurent Pinchart
Hi Dan, Thank you for the patch. On Friday 25 Nov 2016 13:28:35 Dan Carpenter wrote: > A recent cleanup introduced a potential dereference of -EFAULT when we > call kfree(map->menu_info). I should have caught that, my apologies :-( Thinking a bit more about this class of problems, would the fol

Re: [patch] [media] uvcvideo: freeing an error pointer

2016-11-25 Thread SF Markus Elfring
> A recent cleanup introduced a potential dereference of -EFAULT when we > call kfree(map->menu_info). > > Fixes: 4cc5bed1caeb ("[media] uvcvideo: Use memdup_user() rather than > duplicating its implementation") > Signed-off-by: Dan Carpenter Thanks for your information. > diff --git a/driver

[patch] [media] uvcvideo: freeing an error pointer

2016-11-25 Thread Dan Carpenter
A recent cleanup introduced a potential dereference of -EFAULT when we call kfree(map->menu_info). Fixes: 4cc5bed1caeb ("[media] uvcvideo: Use memdup_user() rather than duplicating its implementation") Signed-off-by: Dan Carpenter diff --git a/drivers/media/usb/uvc/uvc_v4l2.c b/drivers/media/us