On Fri, Sep 18 2009 at 12:26pm -0400, Jun'ichi Nomura <j-nomura@xxxxxxxxxxxxx> wrote: > Use new blk_queue_copy_limits() so that invalid limits > (max_sectors == 0) are fixed up appropriately when copied to the queue. > > Signed-off-by: Kiyoshi Ueda <k-ueda@xxxxxxxxxxxxx> > Signed-off-by: Jun'ichi Nomura <j-nomura@xxxxxxxxxxxxx> > Reported-by: David Strand <dpstrand@xxxxxxxxx> > Cc: Mike Snitzer <snitzer@xxxxxxxxxx> > Cc: Alasdair G Kergon <agk@xxxxxxxxxx> > Cc: Martin K. Petersen <martin.petersen@xxxxxxxxxx> > Cc: Jens Axboe <jens.axboe@xxxxxxxxxx> > --- > drivers/md/dm-table.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > Index: linux-2.6.31.work/drivers/md/dm-table.c > =================================================================== > --- linux-2.6.31.work.orig/drivers/md/dm-table.c > +++ linux-2.6.31.work/drivers/md/dm-table.c > @@ -1090,7 +1090,7 @@ void dm_table_set_restrictions(struct dm > /* > * Copy table's limits to the DM device's request_queue > */ > - q->limits = *limits; > + blk_queue_copy_limits(q, limits); > > if (limits->no_cluster) > queue_flag_clear_unlocked(QUEUE_FLAG_CLUSTER, q); How about just having 2 patches in the series and folding the above DM change into the first patch? Doesn't _really_ matter I guess... Anyway, these minor points aside: I like what you've done with this series. Acked-by: Mike Snitzer <snitzer@xxxxxxxxxx> -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
