On Sat, Nov 10, 2012 at 09:00:15AM +0530, viresh kumar wrote:
> On Sat, Nov 10, 2012 at 2:27 AM, Jon Mason wrote:
> > device_control is an optional and not implemented in all DMA drivers.
> > Any calls to these will result in a NULL pointer dereference. dmatest
> > makes two of these calls when
On Sat, Nov 10, 2012 at 09:00:15AM +0530, viresh kumar wrote:
On Sat, Nov 10, 2012 at 2:27 AM, Jon Mason jon.ma...@intel.com wrote:
device_control is an optional and not implemented in all DMA drivers.
Any calls to these will result in a NULL pointer dereference. dmatest
makes two of these
On Sat, Nov 10, 2012 at 2:27 AM, Jon Mason wrote:
> device_control is an optional and not implemented in all DMA drivers.
> Any calls to these will result in a NULL pointer dereference. dmatest
> makes two of these calls when completing the kernel thread and removing
> the module. These are
device_control is an optional and not implemented in all DMA drivers.
Any calls to these will result in a NULL pointer dereference. dmatest
makes two of these calls when completing the kernel thread and removing
the module. These are corrected by calling the dmaengine_device_control
wrapper and
device_control is an optional and not implemented in all DMA drivers.
Any calls to these will result in a NULL pointer dereference. dmatest
makes two of these calls when completing the kernel thread and removing
the module. These are corrected by calling the dmaengine_device_control
wrapper and
On Sat, Nov 10, 2012 at 2:27 AM, Jon Mason jon.ma...@intel.com wrote:
device_control is an optional and not implemented in all DMA drivers.
Any calls to these will result in a NULL pointer dereference. dmatest
makes two of these calls when completing the kernel thread and removing
the module.
6 matches
Mail list logo