Re: [PATCH] MUSB: fix memory corruption when using more than max endpoints

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 10, 2008 at 01:36:16PM +0300, ext Felipe Balbi wrote:
> Let's keep linux-usb on the loop for musb related patches ;-)
> 
> On Wed, Sep 10, 2008 at 08:53:56AM +0300, ext Kevin Hilman wrote:
> > There is no check if platform code passes in more endpoints (num_eps)
> > than the maximum number of enpoints (MUSB_C_NUM_EPS.)  The result is
> > that allocate_instance() happily writes past the end of 'struct musb'
> > corrupting memory.
> > 
> > The fix below increases the max to 32 (used on omap3) and also adds a
> > BUG() if the platform code requests more than the max.
> > 
> > This memory corruption was triggering various forms of crashes/panics
> > with kmem_cache_alloc() in the backtrace.
> > 
> > Signed-off-by: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx>

Could you update this patch without the last change of max endpoints ???

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux