diff options
author | Nicolai Stange <nicstange@gmail.com> | 2016-03-22 13:18:07 +0100 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2016-04-05 20:35:51 +0800 |
commit | 85d541a3d14ab7a4e08c280740d9a7e097b04835 (patch) | |
tree | 911836bb1c5fb48923c747a587b076797725044e /lib/mpi/generic_mpih-add1.c | |
parent | 64c09b0b59b92ad231dd526f57f24139b728044b (diff) | |
download | linux-85d541a3d14ab7a4e08c280740d9a7e097b04835.tar.gz linux-85d541a3d14ab7a4e08c280740d9a7e097b04835.tar.bz2 linux-85d541a3d14ab7a4e08c280740d9a7e097b04835.zip |
lib/mpi: mpi_read_raw_from_sgl(): sanitize meaning of indices
Within the byte reading loop in mpi_read_raw_sgl(), there are two
housekeeping indices used, z and x.
At all times, the index z represents the number of output bytes covered
by the input SGEs for which processing has completed so far. This includes
any leading zero bytes within the most significant limb.
The index x changes its meaning after the first outer loop's iteration
though: while processing the first input SGE, it represents
"number of leading zero bytes in most significant output limb" +
"current position within current SGE"
For the remaining SGEs OTOH, x corresponds just to
"current position within current SGE"
After all, it is only the sum of z and x that has any meaning for the
output buffer and thus, the
"number of leading zero bytes in most significant output limb"
part can be moved away from x into z from the beginning, opening up the
opportunity for cleaner code.
Before the outer loop iterating over the SGEs, don't initialize z with
zero, but with the number of leading zero bytes in the most significant
output limb. For the inner loop iterating over a single SGE's bytes,
get rid of the buf_shift offset to x' bounds and let x run from zero to
sg->length - 1.
Signed-off-by: Nicolai Stange <nicstange@gmail.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'lib/mpi/generic_mpih-add1.c')
0 files changed, 0 insertions, 0 deletions