Omar,
static void omap_mbox_fini(struct omap_mbox *mbox)
{
+ if (!--mbox-use_count) {
+ tasklet_kill(mbox-txq-tasklet);
+ flush_work(mbox-rxq-work);
+ mbox_queue_free(mbox-txq);
+ mbox_queue_free(mbox-rxq);
+ }
+
+
Hi,
On 10/14/2010 9:13 PM, Hari Kanigeri wrote:
@@ -252,41 +253,39 @@ static int omap_mbox_startup(struct omap_mbox *mbox)
...
+ if (!mbox-use_count++) {
+ ret = request_irq(mbox-irq, mbox_interrupt, IRQF_SHARED,
+ mbox-name, mbox);
In the current mailbox driver, the mailbox internal pointer for
callback can be directly manipulated by the Users, so a second
User can easily corrupt the first user's callback pointer.
The initial effort to correct this issue can be referred here:
https://patchwork.kernel.org/patch/107520/
Along
In the current mailbox driver, the mailbox internal pointer for
callback can be directly manipulated by the Users, so a second
User can easily corrupt the first user's callback pointer.
The initial effort to correct this issue can be referred here:
https://patchwork.kernel.org/patch/107520/
Along
In the current mailbox driver, the mailbox internal pointer for
callback can be directly manipulated by the Users, so a second
User can easily corrupt the first user's callback pointer.
The initial effort to correct this issue can be referred here:
https://patchwork.kernel.org/patch/107520/
Along
