About `bio->bi_iter.bi_size` at write endio time

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Recently I got a strange case where for write bio, at its endio time, I got bio->bi_iter.bi_size == 0, but bio_for_each_segment_all() reports we still have some bv_len.

And obviously, when the bio get submitted, its bi_size is not 0.

This is especially common for REQ_OP_ZONE_APPEND bio, but I also get rare bi_size == 0 at endio time, for REQ_OP_WRITE too.

So I guess bi_size at endio time is no longer reliable due to bio merging/splitting?

Thus the only correct way to get how large a bio really is, is through bio_for_each_segment_all()?

Thanks,
Qu



[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux