From: Peter Xu <peterx@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Junjie Cao <junjie.cao@intel.com>,
qemu-devel@nongnu.org, farosas@suse.de
Subject: Re: [PATCH v2 0/3] migration/file: fix type mismatch and NULL deref in multifd_file_recv_data
Date: Thu, 26 Mar 2026 11:21:08 -0400 [thread overview]
Message-ID: <acVO5HUVb18FlIYf@x1.local> (raw)
In-Reply-To: <acJtbvE39JHM4g5c@redhat.com>
On Tue, Mar 24, 2026 at 10:54:38AM +0000, Daniel P. Berrangé wrote:
> On Tue, Mar 24, 2026 at 04:27:38PM +0800, Junjie Cao wrote:
> > Hi Peter, Daniel,
> >
> > I wanted to follow up on this series. Looking back, I went
> > straight to adding new public API in io/channel. I should
> > have confirmed my approach and whether the Suggested-by
> > tag was appropriate here with you before sending. Sorry for that.
> >
> > I see two possible paths and would appreciate your guidance:
> >
> > (a) Keep it purely a fix in migration/file.c: add a local
> > retry loop around qio_channel_pread() in
> > multifd_file_recv_data(), fix the ssize_t/size_t
> > mismatch, and use ERRP_GUARD() so error_prepend()
> > is safe.
> >
> > (b) If pread_all() retry helpers are worth having as a
> > general facility in io/channel, I'm happy to propose
> > them as a separate RFC so we can discuss the API design
> > on its own merits.
> >
> > I'm leaning toward (a) and can send a v3 quickly.
> > Does that sound right?
>
> Doing (b) is the right approach. We want these helpers in the
> general code, so we don't create technical debt that has to be
> fixed next time something else wants the same APIs.
Sorry for a late response, Junjie. I agree with Dan.
--
Peter Xu
prev parent reply other threads:[~2026-03-26 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 8:46 [PATCH] migration/file: fix type mismatch and NULL deref in multifd_file_recv_data Junjie Cao
2026-03-16 20:41 ` Peter Xu
2026-03-17 8:58 ` Daniel P. Berrangé
2026-03-18 14:01 ` [PATCH v2 0/3] " Junjie Cao
2026-03-18 14:01 ` [PATCH v2 1/3] io/channel: introduce qio_channel_pread{v, }_all() and preadv_all_eof() Junjie Cao
2026-03-24 10:51 ` Daniel P. Berrangé via qemu development
2026-03-18 14:01 ` [PATCH v2 2/3] migration/file: fix type mismatch and NULL deref in multifd_file_recv_data Junjie Cao
2026-03-24 10:53 ` Daniel P. Berrangé
2026-03-18 14:01 ` [PATCH v2 3/3] tests/unit: add pread_all and preadv_all tests for io channel file Junjie Cao
2026-03-24 8:27 ` [PATCH v2 0/3] migration/file: fix type mismatch and NULL deref in multifd_file_recv_data Junjie Cao
2026-03-24 10:54 ` Daniel P. Berrangé
2026-03-26 15:21 ` Peter Xu [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=acVO5HUVb18FlIYf@x1.local \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=junjie.cao@intel.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