linux-kernel - [git pull] Further device-mapper fixes for 3.5

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:	Fri, 20 Jul 2012 15:28:21 +0100
From:	Alasdair G Kergon <agk@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	dm-devel@...hat.com, linux-kernel@...r.kernel.org,
	Joe Thornber <ejt@...hat.com>,
	Mike Snitzer <snitzer@...hat.com>, stable@...r.kernel.org,
	Zdenek Kabelac <zkabelac@...hat.com>,
	Mikulas Patocka <mpatocka@...hat.com>
Subject: [git pull] Further device-mapper fixes for 3.5

Please pull from:
 
  git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm tags/dm-3.5-fixes-2

to get the following further device-mapper fixes for 3.5.
 
Thanks,
Alasdair
  
----------------------------------------------------------------
Three fixes for device-mapper discard processing:
  - avoid a crash in dm-raid1 when discards coincide with mirror recovery;
  - avoid discarding shared data that's still needed in dm-thin;
  - don't guarantee that discarded blocks will be wiped in dm-raid1.

----------------------------------------------------------------
Mikulas Patocka (3):
      dm raid1: fix crash with mirror recovery and discard
      dm thin: do not send discards to shared blocks
      dm raid1: set discard_zeroes_data_unsupported

 drivers/md/dm-raid1.c       |    3 ++-
 drivers/md/dm-region-hash.c |    5 ++++-
 drivers/md/dm-thin.c        |    6 +++++-
 3 files changed, 11 insertions(+), 3 deletions(-)
--
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/