On Wed, May 23, 2012 at 05:02:40PM -0700, Kent Overstreet wrote:
> This consolidates some code, and will help in a later patch changing how
> bio cloning works.
Which consolidations are happening and which drivers are being
affected how?
> diff --git a/drivers/md/dm.c b/drivers/md/dm.c
> index e6e7b19..e5076f2 100644
> --- a/drivers/md/dm.c
> +++ b/drivers/md/dm.c
> @@ -1062,26 +1062,19 @@ static struct bio *split_bvec(struct bio *bio, sector_t sector,
> * Creates a bio that consists of range of complete bvecs.
> */
> static struct bio *clone_bio(struct bio *bio, sector_t sector,
> - unsigned short idx, unsigned short bv_count,
> + unsigned short bv_count,
> unsigned int len, struct bio_set *bs)
> {
> struct bio *clone;
>
> - clone = bio_alloc_bioset(GFP_NOIO, bio->bi_max_vecs, bs);
> - __bio_clone(clone, bio);
> + clone = bio_clone_bioset(bio, GFP_NOIO, bs);
> clone->bi_sector = sector;
> - clone->bi_idx = idx;
> - clone->bi_vcnt = idx + bv_count;
> + clone->bi_vcnt = bv_count;
> clone->bi_size = to_bytes(len);
> - clone->bi_flags &= ~(1 << BIO_SEG_VALID);
Why is this safe? If it's only bioset related API changes, why are
there other changes at all? If the new clone interface can handle
bioset fine, do we still need to expose __bio_clone()?
> - if (bio_integrity(bio)) {
> - bio_integrity_clone(clone, bio, GFP_NOIO, bs);
> -
> - if (idx != bio->bi_idx || clone->bi_size < bio->bi_size)
> - bio_integrity_trim(clone,
> - bio_sector_offset(bio, idx, 0), len);
> - }
> + if (bio_integrity(bio) &&
> + clone->bi_size < bio->bi_size)
> + bio_integrity_trim(clone, 0, len);
Why is idx != bi_idx test dropped?
I'm gonna stop here on this series. It doesn't seem like the issues
pointed out before have been addressed. I recommend spending more
effort on patch descriptions. Writing descriptions is not only
important for reviewing and history but it's a good step in ensuring
the patches are sane and properly split. If you can't explain each
change in the patch, it generally means either the changes themselves
are wrong or wrongly split.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
