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

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: <20150203192902.GA6074@kernel.dk>
Date:	Tue, 3 Feb 2015 12:29:02 -0700
From:	Jens Axboe <axboe@...com>
To:	<torvalds@...uxfoundation.org>
CC:	<linux-kernel@...r.kernel.org>
Subject: [GIT PULL] Final block fixes for 3.19

Hi Linus,

Unfortunately the hctx/ctx lifetime fix from last pull had some issues.
This pull request contains a revert of the problematic commit, and a
proper rewrite of it. The rewrite has been tested by the users
complaining about the regression, and it works fine now. Additionally,
I've run testing on all the blk-mq use cases for it and it passes. So we
should definitely get this into 3.19, to avoid regression for some
cases.

Please pull!

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

for you to fetch changes up to e09aae7edec1d20824c60a6f0ca4589f99ada17b:

  blk-mq: release mq's kobjects in blk_release_queue() (2015-01-29 08:30:51 -0800)

----------------------------------------------------------------
Ming Lei (2):
      Revert "blk-mq: fix hctx/ctx kobject use-after-free"
      blk-mq: release mq's kobjects in blk_release_queue()

 block/blk-mq-sysfs.c | 25 ++-----------------------
 block/blk-mq.c       | 23 +++++++++++++++++++++--
 block/blk-mq.h       |  2 ++
 block/blk-sysfs.c    |  2 ++
 4 files changed, 27 insertions(+), 25 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/