linux-kernel - [git pull] device mapper fixes for 3.16-rc6

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:	Thu, 17 Jul 2014 23:03:58 -0400
From:	Mike Snitzer <snitzer@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	dm-devel@...hat.com, linux-kernel@...r.kernel.org,
	Alasdair G Kergon <agk@...hat.com>,
	Joe Thornber <ejt@...hat.com>
Subject: [git pull] device mapper fixes for 3.16-rc6

Hi Linus,

The following changes since commit 7a7a3b45fed9a144dbf766ee842a4c5d0632b81d:

  dm mpath: fix IO hang due to logic bug in multipath_busy (2014-07-10 16:44:15 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/dm-3.16-fixes-2

for you to fetch changes up to 048e5a07f282c57815b3901d4a68a77fa131ce0a:

  dm cache metadata: do not allow the data block size to change (2014-07-15 14:07:50 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
Fix the dm-thinp and dm-cache targets to disallow changing the data
device's block size.

----------------------------------------------------------------
Mike Snitzer (2):
      dm thin metadata: do not allow the data block size to change
      dm cache metadata: do not allow the data block size to change

 drivers/md/dm-cache-metadata.c | 9 +++++++++
 drivers/md/dm-thin-metadata.c  | 9 +++++++++
 2 files changed, 18 insertions(+)
--
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/