linux-kernel - Re: [PATCH] md: Add support for data integrity to MD

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>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 29 Sep 2008 10:51:54 -0400
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Neil Brown <neilb@...e.de>
Cc:	"Martin K. Petersen" <martin.petersen@...cle.com>,
	jens.axboe@...cle.com, linux-kernel@...r.kernel.org,
	linux-raid@...r.kernel.org
Subject: Re: [PATCH] md: Add support for data integrity to MD

>>>>> "Neil" == Neil Brown <neilb@...e.de> writes:

Neil> But what if we subsequently add a different device to that array
Neil> which uses a different protection format.  Would we be able to
Neil> tell the filesystem that integrity protection isn't available
Neil> any more?  Or can we detect if the filesystem is using integrity
Neil> protection, and reject the new device if it doesn't match?

Generally the filesystem will look at the block device's integrity
profile every time it prepares an I/O.  So if we add a subdevice and
detect a mismatch the mddev integrity profile should be removed.

Neil> In either case, some extra handling is needed in
Neil> bind_rdev_to_array.

This code has been sitting in my patch queue for several months
waiting for the core of the integrity stuff to go in.  So I'm a bit
fuzzy on the details.  I'll take a look...

-- 
Martin K. Petersen	Oracle Linux Engineering

--
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/