This patch doesn't quite look like a fix to me: The megaraid mailboxes
are always >16 bytes *but* none of the setting commands is supposed to
touch any of the status parts (which begin at byte 15), so I don't see
how your patch would prevent a panic.
It also looks like the first fifteen (not sixteen) bytes are user data
and the remaining 51 are for data from the card.
It thus looks like this memcpy in both issue_scb() and issue_scb_block()
may be wrong
memcpy((char *)mbox, (char *)scb->raw_mbox, 16);
because it's overwriting the mbox->busy return.
Logically, it looks like the mbox_t should be split up into an mbox_out
(which is what all the routines want to set values in) and an mbox_in
which is where the status is returned.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/