[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 0/1] fallocate missing fd_offset
From: |
“William Roche |
Subject: |
[PATCH 0/1] fallocate missing fd_offset |
Date: |
Tue, 21 Jan 2025 17:59:55 +0000 |
From: William Roche <william.roche@oracle.com>
Working on the poisoned memory recovery mechanisms with David
Hildenbrand, it appeared that the file hole punching done with
the memory discard functions are missing the file offset value
fd_offset to correctly modify the right file location.
I'm not sure that guest_memfd would use a non zero fd_offset, but I'm
also modifying the ram_block_discard_guest_memfd_range() function to
include this fallocate use case too.
The fix is checkpatch.pl clean
make check runs fine on both ARM and x86
William Roche (1):
system/physmem: take into account fd_offset for file fallocate
system/physmem.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
--
2.43.5
- [PATCH 0/1] fallocate missing fd_offset,
“William Roche <=