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
| ||
|
Date: Mon, 9 Jul 2012 10:57:12 -0400 From: Mike Snitzer <snitzer@...hat.com> To: "Chauhan, Vijay" <Vijay.Chauhan@...app.com> Cc: "dm-devel@...hat.com" <dm-devel@...hat.com>, "Moger, Babu" <Babu.Moger@...app.com>, "Martin K. Petersen" <martin.petersen@...cle.com>, "Stankey, Robert" <Robert.Stankey@...app.com>, axboe@...nel.dk, linux-kernel@...r.kernel.org Subject: [PATCH v2] block: do not artificially constrain max_sectors for stacking drivers blk_set_stacking_limits() is intended to allow stacking drivers to build up the limits of the stacked device based on the underlying devices' limits. But in the case of 'max_sectors' the default of BLK_DEF_MAX_SECTORS (1024) doesn't allow the stacking driver to inherit a max_sectors larger than 1024. It is now clear that this artificial limit is getting in the way so change blk_set_stacking_limits's max_sectors to UINT_MAX (which allows stacking drivers like dm-multipath to inherit 'max_sectors' from the underlying paths). blk_limits_max_hw_sectors() must allow stacking drivers to not have max_sectors set to BLK_DEF_MAX_SECTORS as a side-effect. Move that historic constraint to blk_queue_max_hw_sectors(). Reported-by: Vijay Chauhan <vijay.chauhan@...app.com> Signed-off-by: Mike Snitzer <snitzer@...hat.com> Cc: Martin K. Petersen <martin.petersen@...cle.com> --- block/blk-settings.c | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) v2: tweak blk_limits_max_hw_sectors and blk_queue_max_hw_sectors diff --git a/block/blk-settings.c b/block/blk-settings.c index d3234fc..b808dfd 100644 --- a/block/blk-settings.c +++ b/block/blk-settings.c @@ -143,8 +143,7 @@ void blk_set_stacking_limits(struct queue_limits *lim) lim->discard_zeroes_data = 1; lim->max_segments = USHRT_MAX; lim->max_hw_sectors = UINT_MAX; - - lim->max_sectors = BLK_DEF_MAX_SECTORS; + lim->max_sectors = UINT_MAX; } EXPORT_SYMBOL(blk_set_stacking_limits); @@ -255,8 +254,7 @@ void blk_limits_max_hw_sectors(struct queue_limits *limits, unsigned int max_hw_ } limits->max_hw_sectors = max_hw_sectors; - limits->max_sectors = min_t(unsigned int, max_hw_sectors, - BLK_DEF_MAX_SECTORS); + limits->max_sectors = min_not_zero(limits->max_sectors, max_hw_sectors); } EXPORT_SYMBOL(blk_limits_max_hw_sectors); @@ -271,6 +269,8 @@ EXPORT_SYMBOL(blk_limits_max_hw_sectors); void blk_queue_max_hw_sectors(struct request_queue *q, unsigned int max_hw_sectors) { blk_limits_max_hw_sectors(&q->limits, max_hw_sectors); + q->limits.max_sectors = min_t(unsigned int, max_hw_sectors, + BLK_DEF_MAX_SECTORS); } EXPORT_SYMBOL(blk_queue_max_hw_sectors); -- 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/
Powered by blists - more mailing lists