linux-kernel - Re: Block integrity patches for 2.6.28

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

Message-ID: <20081002105632.GF19428@kernel.dk>
Date:	Thu, 2 Oct 2008 12:56:32 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	"Martin K. Petersen" <martin.petersen@...cle.com>
Cc:	neilb@...e.de, agk@...rceware.org, linux-kernel@...r.kernel.org,
	dm-devel@...hat.com
Subject: Re: Block integrity patches for 2.6.28

On Wed, Oct 01 2008, Martin K. Petersen wrote:
> 
> This patch series contains block layer integrity updates for 2.6.28.
> 
> There are a few fixes to the core bits, including a switch from
> block_device to gendisk in the integrity compare function.  I also had
> to add a helper to access a gendisk's integrity profile.  This is used
> by MD.
> 
> The DM bits have been cleaned up and a separate dm_table_set_integrity
> function has been introduced.  This allows us to avoid changing
> dm_table_set_restrictions() and its callers.
> 
> The MD patch now correctly handles devices that come and go (as
> requested by Neil).
> 
> The patches are against for-2.6.28 and depend on
> 
>     d7533ad0e132f92e75c1b2eb7c26387b25a583c1

As far as I can tell, most of that commit is still fine. You want
bdev_get_integrity() in blkdev.h, the 3 other moves and the unused
bdev_get_tag_size() do not look like they are being used by this patch
set.

Correct?

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