[GIT PULL] Important block fixes for 3.7

[Jens Axboe]

Hi Linus,

Distilled down version of bug fixes for 3.7. The patches have been well
tested. If you notice that commit dates are from today, it's because I
pulled less important bits out and shuffled them into the 3.8 mix. Apart
from that, no changes, base still the same.

It contains:

- Fix for aoe, don't run request_fn while it's plugged.

- Fix for a regression in floppy since 3.6, which causes
  problems if no floppy is found.

- Stable fix for blk_exec(), don't touch a request after it
  has been sent to the scheduler (and the device as well).

- Five fixes for various nasties in mtip32xx.

Please pull.

  git://git.kernel.dk/linux-block.git for-linus

----------------------------------------------------------------
for-linus-20121123

----------------------------------------------------------------
Ed L. Cashin (1):
      aoe: avoid running request handler on plugged queue

Jens Axboe (2):
      dm: fix deadlock with request based dm and queue request_fn recursion
      mtip32xx: fix shift larger than type warning

Jiri Kosina (1):
      floppy: destroy floppy workqueue before cleaning up the queue

Roland Dreier (1):
      block: Don't access request after it might be freed

Selvan Mani (4):
      mtip32xx: fix potential crash on SEC_ERASE_UNIT
      mtip32xx: Fix to make lba address correct in big-endian systems
      mtip32xx: Fix incorrect mask used for erase mode
      mtip32xx: Fix padding issue

Wei Yongjun (1):
      mtip32xx: fix potential NULL pointer dereference in mtip_timeout_function()

 block/blk-exec.c                  |  8 +++++++-
 drivers/block/aoe/aoecmd.c        |  2 +-
 drivers/block/floppy.c            |  5 +++--
 drivers/block/mtip32xx/mtip32xx.c | 18 ++++++++++++------
 drivers/block/mtip32xx/mtip32xx.h |  6 +++---
 drivers/md/dm.c                   |  8 +++++++-
 6 files changed, 33 insertions(+), 14 deletions(-)

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/