diff options
| author |   Mikulas Patocka <mpatocka@redhat.com> | 2023-12-05 16:39:16 +0100 |
|---|---|---|
| committer |   Mike Snitzer <snitzer@kernel.org> | 2023-12-18 13:11:05 -0500 |
| commit | b86f4b790c998afdbc88fe1aa55cfe89c4068726 (patch) | |
| tree | 1a09a97a61269b74a4d0bb4ec2c86bd072118ffd /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | dm-raid: delay flushing event_work() after reconfig_mutex is released (diff) | |
| download | wireguard-linux-b86f4b790c998afdbc88fe1aa55cfe89c4068726.tar.xz wireguard-linux-b86f4b790c998afdbc88fe1aa55cfe89c4068726.zip | |
dm-integrity: don't modify bio's immutable bio_vec in integrity_metadata()
__bio_for_each_segment assumes that the first struct bio_vec argument
doesn't change - it calls "bio_advance_iter_single((bio), &(iter),
(bvl).bv_len)" to advance the iterator. Unfortunately, the dm-integrity
code changes the bio_vec with "bv.bv_len -= pos". When this code path
is taken, the iterator would be out of sync and dm-integrity would
report errors. This happens if the machine is out of memory and
"kmalloc" fails.
Fix this bug by making a copy of "bv" and changing the copy instead.
Fixes: 7eada909bfd7 ("dm: add integrity target")
Cc: stable@vger.kernel.org # v4.12+
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions