On Tue, Oct 31 2006, NeilBrown wrote: > This would be good for 2.6.19 and even 18.2, if it is seens acceptable. > raid0 at least (possibly other) can be made to Oops with a bad partition > table and best fix seem to be to not let out-of-range request get down > to the device. > > ### Comments for Changeset > > Partitions are not limited to live within a device. So > we should range check after partition mapping. > > Note that 'maxsector' was being used for two different things. I have > split off the second usage into 'old_sector' so that maxsector can be > still be used for it's primary usage later in the function. > > Cc: Jens Axboe <jens.axboe@xxxxxxxxxx> > Signed-off-by: Neil Brown <neilb@xxxxxxx> Code looks good to me, but for some reason your comment exceeds 80 chars. Can you please fix that up? Acked-by: Jens Axboe <jens.axboe@xxxxxxxxxx> -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
