From: Konstantin Kostiuk <kkostiuk@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] qga: Add log to guest-fsfreeze-thaw command
Date: Mon, 9 Dec 2024 13:40:37 +0200 [thread overview]
Message-ID: <CAPMcbCqKRftWUitBpgq1bzDcNV8GCPPxMJahL0ozf11D=qgHDA@mail.gmail.com> (raw)
In-Reply-To: <Z1bU5g4jnppsi4Xf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1807 bytes --]
Best Regards,
Konstantin Kostiuk.
On Mon, Dec 9, 2024 at 1:30 PM Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Mon, Dec 09, 2024 at 01:18:17PM +0200, Konstantin Kostiuk wrote:
> > Signed-off-by: Konstantin Kostiuk <kkostiuk@redhat.com>
> > ---
> > qga/commands-posix.c | 3 +++
> > qga/commands-win32.c | 2 ++
> > 2 files changed, 5 insertions(+)
> >
> > diff --git a/qga/commands-posix.c b/qga/commands-posix.c
> > index 636307bedf..ac8d150582 100644
> > --- a/qga/commands-posix.c
> > +++ b/qga/commands-posix.c
> > @@ -805,6 +805,9 @@ int64_t qmp_guest_fsfreeze_thaw(Error **errp)
> > int ret;
> >
> > ret = qmp_guest_fsfreeze_do_thaw(errp);
> > +
> > + slog("guest-fsthaw called");
>
> If ret < 0, then thawing failed and surely it is potentially
> unsafe to log ?
>
>
Potentially yes, but we have similar in guest_fsfreeze_cleanup.
We print the log when qmp_guest_fsfreeze_thaw fails.
> > +
> > if (ret >= 0) {
> > ga_unset_frozen(ga_state);
> > execute_fsfreeze_hook(FSFREEZE_HOOK_THAW, errp);
> > diff --git a/qga/commands-win32.c b/qga/commands-win32.c
> > index 038beb8cfa..3a6f3ac7c5 100644
> > --- a/qga/commands-win32.c
> > +++ b/qga/commands-win32.c
> > @@ -1272,6 +1272,8 @@ int64_t qmp_guest_fsfreeze_thaw(Error **errp)
> >
> > qga_vss_fsfreeze(&i, false, NULL, errp);
> >
> > + slog("guest-fsthaw called");
> > +
> > ga_unset_frozen(ga_state);
> > return i;
> > }
> > --
> > 2.47.1
> >
>
> With regards,
> Daniel
> --
> |: https://berrange.com -o-
> https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o-
> https://www.instagram.com/dberrange :|
>
>
[-- Attachment #2: Type: text/html, Size: 3266 bytes --]
prev parent reply other threads:[~2024-12-09 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 11:18 [PATCH] qga: Add log to guest-fsfreeze-thaw command Konstantin Kostiuk
2024-12-09 11:30 ` Daniel P. Berrangé
2024-12-09 11:40 ` Konstantin Kostiuk [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='CAPMcbCqKRftWUitBpgq1bzDcNV8GCPPxMJahL0ozf11D=qgHDA@mail.gmail.com' \
--to=kkostiuk@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=michael.roth@amd.com \
--cc=philmd@linaro.org \
--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).