[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1366389740-19587-1-git-send-email-linkinjeon@gmail.com>
Date: Sat, 20 Apr 2013 01:42:20 +0900
From: Namjae Jeon <linkinjeon@...il.com>
To: dwmw2@...radead.org, axboe@...nel.dk, shli@...nel.org,
Paul.Clements@...eleye.com, npiggin@...nel.dk, neilb@...e.de,
cjb@...top.org, adrian.hunter@...el.com,
James.Bottomley@...senPartnership.com, JBottomley@...allels.com
Cc: linux-scsi@...r.kernel.org, linux-mtd@...ts.infradead.org,
nbd-general@...ts.sourceforge.net, linux-raid@...r.kernel.org,
linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
jcmvbkbc@...il.com, Namjae Jeon <linkinjeon@...il.com>,
Namjae Jeon <namjae.jeon@...sung.com>,
Vivek Trivedi <t.vivek@...sung.com>
Subject: [PATCH v2 8/9] dm thin: use generic helper to set max_discard_sectors
From: Namjae Jeon <namjae.jeon@...sung.com>
It is better to use blk_queue_max_discard_sectors helper
function to set max_discard_sectors as it checks
max_discard_sectors upper limit UINT_MAX >> 9
similar issue was reported for mmc in below link
https://lkml.org/lkml/2013/4/1/292
If multiple discard requests get merged, merged discard request's
size exceeds 4GB, there is possibility that merged discard request's
__data_len field may overflow.
This patch fixes this issue.
Signed-off-by: Namjae Jeon <namjae.jeon@...sung.com>
Signed-off-by: Vivek Trivedi <t.vivek@...sung.com>
---
drivers/md/dm-thin.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/md/dm-thin.c b/drivers/md/dm-thin.c
index 905b75f..237295a 100644
--- a/drivers/md/dm-thin.c
+++ b/drivers/md/dm-thin.c
@@ -2513,7 +2513,8 @@ static void set_discard_limits(struct pool_c *pt, struct queue_limits *limits)
struct pool *pool = pt->pool;
struct queue_limits *data_limits;
- limits->max_discard_sectors = pool->sectors_per_block;
+ blk_queue_max_discard_sectors(bdev_get_queue(pt->data_dev->bdev),
+ pool->sectors_per_block);
/*
* discard_granularity is just a hint, and not enforced.
--
1.7.9.5
--
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