From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>,
Peter Xu <peterx@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>,
Alexander Bulekov <alxndr@bu.edu>
Subject: Re: [PATCH] softmmu: Use memmove in flatview_write_continue
Date: Tue, 31 Jan 2023 00:03:32 +0100 [thread overview]
Message-ID: <340d48d4-b6b3-d34d-2705-aa1421360b44@linaro.org> (raw)
In-Reply-To: <20230130135152.76882-1-akihiko.odaki@daynix.com>
On 30/1/23 14:51, Akihiko Odaki wrote:
> We found a case where the source passed to flatview_write_continue() may
> overlap with the destination when fuzzing igb, a new proposed network
> device with sanitizers.
>
> igb uses pci_dma_map() to get Tx packet, and pci_dma_write() to write Rx
> buffer. While pci_dma_write() is usually used to write data from
> memory not mapped to the guest, if igb is configured to perform
> loopback, the data will be sourced from the guest memory. The source and
> destination can overlap and the usage of memcpy() will be invalid in
> such a case.
>
> While we do not really have to deal with such an invalid request for
> igb, detecting the overlap in igb code beforehand requires complex code,
> and only covers this specific case. Instead, just replace memcpy() with
> memmove() to torelate overlaps. Using memmove() will slightly damage the
"tolerate"?
> performance as it will need to check overlaps before using SIMD
> instructions for copying, but the cost should be negiligble, considering
"negligible"
> the inherent complexity of flatview_write_continue().
>
> The test cases generated by the fuzzer is available at:
> https://patchew.org/QEMU/20230129053316.1071513-1-alxndr@bu.edu/
>
> The fixed test case is:
> fuzz/crash_47dfe62d9f911bf523ff48cd441b61c0013ed805
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> softmmu/physmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/softmmu/physmem.c b/softmmu/physmem.c
> index cb998cdf23..3cd27b1c9d 100644
> --- a/softmmu/physmem.c
> +++ b/softmmu/physmem.c
> @@ -2828,7 +2828,7 @@ static MemTxResult flatview_write_continue(FlatView *fv, hwaddr addr,
> } else {
> /* RAM case */
> ram_ptr = qemu_ram_ptr_length(mr->ram_block, addr1, &l, false);
> - memcpy(ram_ptr, buf, l);
> + memmove(ram_ptr, buf, l);
> invalidate_and_set_dirty(mr, addr1, l);
> }
>
prev parent reply other threads:[~2023-01-30 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 13:51 [PATCH] softmmu: Use memmove in flatview_write_continue Akihiko Odaki
2023-01-30 16:37 ` Peter Xu
2023-01-30 20:03 ` Alexander Bulekov
2023-01-30 20:28 ` Peter Xu
2023-01-30 23:49 ` Alexander Bulekov
2023-01-30 23:03 ` Philippe Mathieu-Daudé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=340d48d4-b6b3-d34d-2705-aa1421360b44@linaro.org \
--to=philmd@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=alxndr@bu.edu \
--cc=david@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).