qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>, peterx@redhat.com
Cc: farosas@suse.de, steven.sistare@oracle.com, alex@shazbot.org,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] migration: set correct list pointer when removing notifier
Date: Fri, 14 Nov 2025 07:37:24 +0100	[thread overview]
Message-ID: <71f97da4-315e-457e-8ac9-c48d04fb4772@redhat.com> (raw)
In-Reply-To: <20251113213545.513453-1-mjrosato@linux.ibm.com>

On 11/13/25 22:35, Matthew Rosato wrote:
> In migration_remove_notifier(), g_slist_remove() will search for and
> potentially remove an entry from the specified list.  The return value
> should be used to update the potentially-changed head pointer of the
> list that was just searched (migration_state_notifiers[mode]) instead
> of the migration blockers list.
> 
> Fixes: dc79c7d5e1 ("migration: multi-mode notifier")
> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
> ---
>   migration/migration.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/migration/migration.c b/migration/migration.c
> index c2daab6bdd..9e787749b2 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -1693,7 +1693,7 @@ void migration_remove_notifier(NotifierWithReturn *notify)
>   {
>       if (notify->notify) {
>           for (MigMode mode = 0; mode < MIG_MODE__MAX; mode++) {
> -            migration_blockers[mode] =
> +            migration_state_notifiers[mode] =
>                   g_slist_remove(migration_state_notifiers[mode], notify);
>           }
>           notify->notify = NULL;


Reviewed-by: Cédric Le Goater <clg@redhat.com>

Thanks,

C.




  reply	other threads:[~2025-11-14  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 21:35 [PATCH] migration: set correct list pointer when removing notifier Matthew Rosato
2025-11-14  6:37 ` Cédric Le Goater [this message]
2025-11-14 15:48 ` Peter Xu

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=71f97da4-315e-457e-8ac9-c48d04fb4772@redhat.com \
    --to=clg@redhat.com \
    --cc=alex@shazbot.org \
    --cc=farosas@suse.de \
    --cc=mjrosato@linux.ibm.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=steven.sistare@oracle.com \
    /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).