[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v4 12/13] migration/ram: Use offset_in_ramblock() in range checks
From: |
David Hildenbrand |
Subject: |
[PATCH v4 12/13] migration/ram: Use offset_in_ramblock() in range checks |
Date: |
Tue, 21 Apr 2020 10:52:59 +0200 |
We never read or write beyond the used_length of memory blocks when
migrating. Make this clearer by using offset_in_ramblock() consistently.
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Cc: "Dr. David Alan Gilbert" <address@hidden>
Cc: Juan Quintela <address@hidden>
Cc: Peter Xu <address@hidden>
Signed-off-by: David Hildenbrand <address@hidden>
---
migration/ram.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index f03bc84692..2a8cd962df 100644
--- a/migration/ram.c
+++ b/migration/ram.c
@@ -1318,8 +1318,8 @@ static bool find_dirty_block(RAMState *rs,
PageSearchStatus *pss, bool *again)
*again = false;
return false;
}
- if ((((ram_addr_t)pss->page) << TARGET_PAGE_BITS)
- >= pss->block->used_length) {
+ if (!offset_in_ramblock(pss->block,
+ ((ram_addr_t)pss->page) << TARGET_PAGE_BITS)) {
/* Didn't find anything in this RAM Block */
pss->page = 0;
pss->block = QLIST_NEXT_RCU(pss->block, next);
@@ -1523,7 +1523,7 @@ int ram_save_queue_pages(const char *rbname, ram_addr_t
start, ram_addr_t len)
rs->last_req_rb = ramblock;
}
trace_ram_save_queue_pages(ramblock->idstr, start, len);
- if (start+len > ramblock->used_length) {
+ if (!offset_in_ramblock(ramblock, start + len - 1)) {
error_report("%s request overrun start=" RAM_ADDR_FMT " len="
RAM_ADDR_FMT " blocklen=" RAM_ADDR_FMT,
__func__, start, len, ramblock->used_length);
@@ -3349,8 +3349,8 @@ static void colo_flush_ram_cache(void)
while (block) {
offset = migration_bitmap_find_dirty(ram_state, block, offset);
- if (((ram_addr_t)offset) << TARGET_PAGE_BITS
- >= block->used_length) {
+ if (!offset_in_ramblock(block,
+ ((ram_addr_t)offset) << TARGET_PAGE_BITS))
{
offset = 0;
block = QLIST_NEXT_RCU(block, next);
} else {
--
2.25.1
- [PATCH v4 04/13] numa: Make all callbacks of ram block notifiers optional, (continued)
- [PATCH v4 04/13] numa: Make all callbacks of ram block notifiers optional, David Hildenbrand, 2020/04/21
- [PATCH v4 05/13] migration/ram: Handle RAM block resizes during precopy, David Hildenbrand, 2020/04/21
- [PATCH v4 02/13] stubs/ram-block: Remove stubs that are no longer needed, David Hildenbrand, 2020/04/21
- [PATCH v4 06/13] exec: Relax range check in ram_block_discard_range(), David Hildenbrand, 2020/04/21
- [PATCH v4 07/13] migration/ram: Discard RAM when growing RAM blocks after ram_postcopy_incoming_init(), David Hildenbrand, 2020/04/21
- [PATCH v4 08/13] migration/ram: Simplify host page handling in ram_load_postcopy(), David Hildenbrand, 2020/04/21
- [PATCH v4 09/13] migration/ram: Consolidate variable reset after placement in ram_load_postcopy(), David Hildenbrand, 2020/04/21
- [PATCH v4 10/13] migration/ram: Handle RAM block resizes during postcopy, David Hildenbrand, 2020/04/21
- [PATCH v4 11/13] migration/multifd: Print used_length of memory block, David Hildenbrand, 2020/04/21
- [PATCH v4 12/13] migration/ram: Use offset_in_ramblock() in range checks,
David Hildenbrand <=
- [PATCH v4 13/13] migration/ram: Tolerate partially changed mappings in postcopy code, David Hildenbrand, 2020/04/21
- Re: [PATCH v4 00/13] migrate/ram: Fix resizing RAM blocks while migrating, David Hildenbrand, 2020/04/30