summaryrefslogtreecommitdiffstats
path: root/crypto/blowfish_common.c
diff options
context:
space:
mode:
authorMing Lei <tom.leiming@gmail.com>2014-10-22 08:30:30 +0800
committerJens Axboe <axboe@fb.com>2014-10-21 19:00:32 -0600
commit76d8137a31139f0d69ecc4177497ad6b8d4f016c (patch)
tree194c64bc760ff1aff6c21f29b9519725b1c2fc1a /crypto/blowfish_common.c
parent432f16e64f50fd4999a476543d04dd52f7a2d753 (diff)
downloadop-kernel-dev-76d8137a31139f0d69ecc4177497ad6b8d4f016c.zip
op-kernel-dev-76d8137a31139f0d69ecc4177497ad6b8d4f016c.tar.gz
blk-merge: recaculate segment if it isn't less than max segments
The problem is introduced by commit 764f612c6c3c231b(blk-merge: don't compute bi_phys_segments from bi_vcnt for cloned bio), and merge is needed if number of current segment isn't less than max segments. Strictly speaking, bio->bi_vcnt shouldn't be used here since it may not be accurate in cases of both cloned bio or bio cloned from, but bio_segments() is a bit expensive, and bi_vcnt is still the biggest number, so the approach should work. Signed-off-by: Ming Lei <tom.leiming@gmail.com> Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'crypto/blowfish_common.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud