All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Arun Menon <armenon@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Juraj Marcin <jmarcin@redhat.com>,
	Mark Kanda <mark.kanda@oracle.com>
Subject: Re: [PATCH 2/3] migration/cpr: Fix coverity report in cpr_exec_persist_state()
Date: Wed, 22 Oct 2025 10:41:29 -0300	[thread overview]
Message-ID: <874irrt5o6.fsf@suse.de> (raw)
In-Reply-To: <aPjTSkQHHCdSdiFv@x1.local>

Peter Xu <peterx@redhat.com> writes:

> On Wed, Oct 22, 2025 at 09:24:25AM -0300, Fabiano Rosas wrote:
>> Remember to copy Oracle folks.
>
> Do you know who's taking this over from Steve?  If we know, we should
> update the MAINTAINERS file.

I'm not sure about maintainership but I'd be already glad to get testing
and reviews. Steve mentioned Mark Kanda on his email. I'm CCing Mark
here and he can tell us about it. =) No pressure, just making sure CPR
work is not falling between the cracks really.


  reply	other threads:[~2025-10-22 13:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 18:41 [PATCH 0/3] migration: A few fixes on coverity reports Peter Xu
2025-10-21 18:41 ` [PATCH 1/3] migration: Fix error leak in postcopy_ram_listen_thread() Peter Xu
2025-10-21 20:45   ` Fabiano Rosas
2025-10-21 21:20     ` Peter Xu
2025-10-21 18:41 ` [PATCH 2/3] migration/cpr: Fix coverity report in cpr_exec_persist_state() Peter Xu
2025-10-21 20:49   ` Fabiano Rosas
2025-10-21 21:29     ` Peter Xu
2025-10-22 12:24       ` Fabiano Rosas
2025-10-22 12:51         ` Peter Xu
2025-10-22 13:41           ` Fabiano Rosas [this message]
2025-10-21 18:41 ` [PATCH 3/3] migration/cpr: Fix UAF in cpr_exec_cb() when execvp() fails Peter Xu
2025-10-21 20:49   ` Fabiano Rosas

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=874irrt5o6.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=armenon@redhat.com \
    --cc=jmarcin@redhat.com \
    --cc=mark.kanda@oracle.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.