linux-kernel - Re: [PATCH for-2.6.37] block: max hardware sectors limit wrapper

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]

Message-ID: <4D0B129B.3070500@fusionio.com>
Date:	Fri, 17 Dec 2010 08:34:51 +0100
From:	Jens Axboe <jaxboe@...ionio.com>
To:	"Martin K. Petersen" <martin.petersen@...cle.com>
CC:	Mike Snitzer <snitzer@...hat.com>,
	Lars Ellenberg <lars.ellenberg@...bit.com>,
	device-mapper development <dm-devel@...hat.com>,
	Mikulas Patocka <mpatocka@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Alasdair G Kergon <agk@...hat.com>,
	"stable@...nel.org" <stable@...nel.org>
Subject: Re: [PATCH for-2.6.37] block: max hardware sectors limit wrapper

On 2010-12-17 00:49, Martin K. Petersen wrote:
>>>>>> "Mike" == Mike Snitzer <snitzer@...hat.com> writes:
> 
> Mike> Implement blk_limits_max_hw_sectors() and make
> Mike> blk_queue_max_hw_sectors() a wrapper around it.
> 
> Mike> DM needs this to avoid setting queue_limits' max_hw_sectors and
> Mike> max_sectors directly.  dm_set_device_limits() now leverages
> Mike> blk_limits_max_hw_sectors() logic to establish the appropriate
> Mike> max_hw_sectors minimum (PAGE_SIZE).  Fixes issue where DM was
> Mike> incorrectly setting max_sectors rather than max_hw_sectors (which
> Mike> caused dm_merge_bvec()'s max_hw_sectors check to be ineffective).
> 
> Acked-by: Martin K. Petersen <martin.petersen@...cle.com>
> 
> Jens, please apply.

Thanks, it's in.

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