linux-kernel - [GIT PULL] Block fixes for 4.2-rc3

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]

Message-ID: <20150724191235.GA1456@kernel.dk>
Date:	Fri, 24 Jul 2015 13:12:35 -0600
From:	Jens Axboe <axboe@...com>
To:	<torvalds@...uxfoundation.org>
CC:	<linux-kernel@...r.kernel.org>
Subject: [GIT PULL] Block fixes for 4.2-rc3

Hi Linus,

Four smaller fixes for the current series. This pull request contains:

- A fix for clones of discard bio's, that can cause data corruption.
  From Martin.

- A fix for null_blk, where in certain queue modes it could access a
  request after it had been freed. From Mike Krinkin.

- An error handling leak fix for blkcg, from Tejun.

- Also from Tejun, export of the functions that a file system needs to
  implement cgroup writeback support.

Please pull!


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


----------------------------------------------------------------
Martin K. Petersen (1):
      block: Do a full clone when splitting discard bios

Mike Krinkin (1):
      null_blk: fix use-after-free problem

Tejun Heo (2):
      blkcg: fix gendisk reference leak in blkg_conf_prep()
      block: export bio_associate_*() and wbc_account_io()

 block/bio.c              | 17 ++++++++++++++---
 block/blk-cgroup.c       |  6 +++++-
 drivers/block/null_blk.c | 18 +++++++++---------
 fs/fs-writeback.c        |  1 +
 4 files changed, 29 insertions(+), 13 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/