RE: videobuf2-vmalloc suspect for corrupted data

2014-04-08 Thread Divneil Wadhawan
Hi Hans, That should be new enough, I see no important differences between 3.4 and 3.14 in this respect. But really, 3.4? We are moving to 3.10 shortly. Question: if you use MEMORY_MMAP instead of USERPTR, does that work? Unfortunately, this activity is pending (need to get it pushed in

videobuf2-vmalloc suspect for corrupted data

2014-04-07 Thread Divneil Wadhawan
Hi, I have a V4L2 capture driver accepting a malloc'ed buffer. The driver is using vb2_vmalloc_memops (../drivers/media/v4l2-core/videobuf2-vmalloc.c) for user-space to kvaddr translation. Randomly, corrupted data is received by user-app. So, the question is regarding the handling of

Re: videobuf2-vmalloc suspect for corrupted data

2014-04-07 Thread Pawel Osciak
Hi Divneil, On Mon, Apr 7, 2014 at 6:56 PM, Divneil Wadhawan divn...@outlook.com wrote: Hi, I have a V4L2 capture driver accepting a malloc'ed buffer. The driver is using vb2_vmalloc_memops (../drivers/media/v4l2-core/videobuf2-vmalloc.c) for user-space to kvaddr translation. Randomly,

RE: videobuf2-vmalloc suspect for corrupted data

2014-04-07 Thread Divneil Wadhawan
Hi Pawel, Thanks for the quick response. Is it possible that your userspace is not always queuing the same userptr memory areas with the same v4l2_buffer index values? No, userptr is always consistent with the index. In fact, when we dump the captured buffer (Transport Stream) in this case,

Re: videobuf2-vmalloc suspect for corrupted data

2014-04-07 Thread Hans Verkuil
On 04/07/2014 12:49 PM, Divneil Wadhawan wrote: Hi Pawel, Thanks for the quick response. Is it possible that your userspace is not always queuing the same userptr memory areas with the same v4l2_buffer index values? No, userptr is always consistent with the index. In fact, when we dump

RE: videobuf2-vmalloc suspect for corrupted data

2014-04-07 Thread Divneil Wadhawan
Hi Hans, Two more questions: Which kernel version are you using? 3.4.58 Which capture driver are you using? It's a TSMUX driver, written locally. Regards, Divneil -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of

RE: videobuf2-vmalloc suspect for corrupted data

2014-04-07 Thread Divneil Wadhawan
Which capture driver are you using? It's a TSMUX driver, written locally. In complete, it's a Multi-INPUT, single output (MUXER) driver, but, currently, it's the capture side fault here. Regards, Divneil -- To unsubscribe from this list: send the line

Re: videobuf2-vmalloc suspect for corrupted data

2014-04-07 Thread Hans Verkuil
On 04/07/2014 01:20 PM, Divneil Wadhawan wrote: Hi Hans, Two more questions: Which kernel version are you using? 3.4.58 That should be new enough, I see no important differences between 3.4 and 3.14 in this respect. But really, 3.4? That's over two years old! If you have control over what