linux-kernel - [GIT PULL] Final block fixes for 3.16

lists.openwall.net		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 linux-cve-announce 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:	Mon, 21 Jul 2014 15:16:42 +0200
From:	Jens Axboe <axboe@...com>
To:	<torvalds@...ux-foundation.org>
CC:	<linux-kernel@...r.kernel.org>
Subject: [GIT PULL] Final block fixes for 3.16

Hi Linus,

Four small fixes that should go into 3.16, have been queued up for a bit
and delayed due to vacation and other euro duties. But here they are.
The pull request contains:

- Fix for a reported crash with shared tagging on SCSI from Christoph.

- A regression fix for drbd. From Lars Ellenberg.

- Hooking up the compat ioctl for BLKZEROOUT, which requires no
  translation. From Mikulas.

- A fix for a regression where we woud crash on queue exit if the
  root_blkg is gone/not there. From Tejun.


Please pull for 3.16!


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


----------------------------------------------------------------
Christoph Hellwig (1):
      block: don't assume last put of shared tags is for the host

Lars Ellenberg (1):
      drbd: fix regression 'out of mem, failed to invoke fence-peer helper'

Mikulas Patocka (1):
      block: provide compat ioctl for BLKZEROOUT

Tejun Heo (1):
      blkcg: don't call into policy draining if root_blkg is already gone

 block/blk-cgroup.c           |  7 +++++++
 block/blk-tag.c              | 33 +++++++--------------------------
 block/compat_ioctl.c         |  1 +
 drivers/block/drbd/drbd_nl.c |  6 ++++++
 4 files changed, 21 insertions(+), 26 deletions(-)

-- 
Jens Axboe

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