lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Thu, 6 Mar 2014 09:53:02 -0700
From:	Jens Axboe <>
To:	Linus Torvalds <>
CC:	<>
Subject: [GIT PULL] Final block fixes for 3.14

Hi Linus,

Small collection of fixes for 3.14-rc. It contains:

- Three minor update to blk-mq from Christoph.

- Reduce number of unaligned (< 4kb) in-flight writes on mtip32xx to 2.
  From Micron.

- Make the blk-mq CPU notify spinlock raw, since it can't be a sleeper
  spinlock on RT. From Mike Galbraith.

- Drop now bogus BUG_ON() for bio iteration with blk integrity. From Nic

Please pull!

  git:// for-linus

Asai Thambi S P (1):
      mtip32xx: Reduce the number of unaligned writes to 2

Christoph Hellwig (3):
      blk-mq: remove blk_mq_alloc_rq
      blk-mq: merge blk_mq_insert_request and blk_mq_run_request
      blk-mq: support partial I/O completions

Mike Galbraith (1):
      rt,blk,mq: Make blk_mq_cpu_notify_lock a raw spinlock

Nicholas Bellinger (1):
      bio-integrity: Drop bio_integrity_verify BUG_ON in post bip->bip_iter world

 block/blk-exec.c                  |   2 +-
 block/blk-flush.c                 |   4 +-
 block/blk-mq-cpu.c                |  14 +++---
 block/blk-mq.c                    | 100 +++++++-------------------------------
 block/blk-mq.h                    |   1 -
 drivers/block/mtip32xx/mtip32xx.h |   2 +-
 fs/bio-integrity.c                |   5 +-
 include/linux/blk-mq.h            |  11 +++--
 8 files changed, 37 insertions(+), 102 deletions(-)

Jens Axboe

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists