linux-kernel - [git pull] device mapper fix for 3.17-rc5

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, 12 Sep 2014 17:10:46 -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>,
	Anssi Hannula <anssi.hannula@....fi>,
	Joe Thornber <ejt@...hat.com>
Subject: [git pull] device mapper fix for 3.17-rc5

Hi Linus,

The following changes since commit d49ec52ff6ddcda178fc2476a109cf1bd1fa19ed:

  dm crypt: fix access beyond the end of allocated space (2014-08-28 14:24:09 -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.17-fix2

for you to fetch changes up to 40aa978eccec61347cd47b97c598df49acde8be5:

  dm cache: fix race causing dirty blocks to be marked as clean (2014-09-10 11:20:47 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
Fix a race in the DM cache target that caused dirty blocks to be marked
as clean.  This could cause no writeback to occur or spurious dirty
block counts.

----------------------------------------------------------------
Anssi Hannula (1):
      dm cache: fix race causing dirty blocks to be marked as clean

 drivers/md/dm-cache-target.c | 4 ++--
 1 file changed, 2 insertions(+), 2 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/