All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Kostiantyn Kostiuk <kkostiuk@redhat.com>
Cc: qemu-devel@nongnu.org, "Yan Vugenfirer" <yvugenfi@redhat.com>,
	"Daniel Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] util: win32: Write hex value when can't get error message
Date: Mon, 21 Jul 2025 11:22:06 +0200	[thread overview]
Message-ID: <87seipkif5.fsf@pond.sub.org> (raw)
In-Reply-To: <CAPMcbCp=PBMSxtTxCMkxigdovaY=MTNLRo6f3BBXNRT6vu4wmw@mail.gmail.com> (Kostiantyn Kostiuk's message of "Mon, 21 Jul 2025 10:07:27 +0300")

Kostiantyn Kostiuk <kkostiuk@redhat.com> writes:

> On Sat, Jul 19, 2025 at 9:27 AM Markus Armbruster <armbru@redhat.com> wrote:
>
>> Kostiantyn Kostiuk <kkostiuk@redhat.com> writes:
>>
>> > g_win32_error_message - translate a Win32 error code
>> > (as returned by GetLastError()) into the corresponding message.
>> >
>> > In the same time, we call error_setg_win32_internal with
>> > error codes from different Windows componets like VSS or
>> > Performance monitor that provides different codes and
>> > can't be converted with g_win32_error_message.
>>
>> Are these error codes from GetLastError()?
>>
>
> No.
> VSS functions directly return an error code.
> Section: Return value -
> https://learn.microsoft.com/en-us/windows/win32/api/vsbackup/nf-vsbackup-ivssbackupcomponents-addtosnapshotset
>
> Performance Counters API can return a system error code or a PDH error code.
> Section: Return value -
> https://learn.microsoft.com/en-us/windows/win32/api/pdh/nf-pdh-pdhopenqueryw
> System error code = GetLastError, PDH error code, something else.
>
> https://learn.microsoft.com/en-us/windows/win32/perfctrs/pdh-error-codes
> FormatMessage requires LoadLibrary(L"pdh.dll") to work properly.

The error code error_setg_win32() takes is passed to
g_win32_error_message().  Contract:

    g_win32_error_message ()

    gchar *
    g_win32_error_message (gint error);

    Translate a Win32 error code (as returned by GetLastError() or
    WSAGetLastError()) into the corresponding message.  The message is
    either language neutral, or in the thread's language, or the user's
    language, the system's language, or US English (see docs for
    FormatMessage()).  The returned string is in UTF-8.  It should be
    deallocated with g_free().

    Parameters

        error error code.

    Returns

        newly-allocated error message

https://www.manpagez.com/html/glib/glib-2.46.0/glib-Windows-Compatibility-Functions.php#g-win32-error-message

Passing error codes from sources other than GetLastError() or
WSAGetLastError() violates this contract.

Apparently, g_win32_error_message() returns NULL then.  This is not
documented behavior.

Your fix relies on this undocumented behavior.

I believe we should instead fix the misuses of error_setg_win32().

[...]



  reply	other threads:[~2025-07-21  9:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17 14:59 [PATCH] util: win32: Write hex value when can't get error message Kostiantyn Kostiuk
2025-07-17 15:28 ` Yan Vugenfirer
2025-07-19  6:27 ` Markus Armbruster
2025-07-21  7:07   ` Kostiantyn Kostiuk
2025-07-21  9:22     ` Markus Armbruster [this message]
2025-07-21 10:12       ` Kostiantyn Kostiuk
2025-07-21 11:23         ` Yan Vugenfirer
2025-07-21 11:53         ` Philippe Mathieu-Daudé
2025-07-25  9:59           ` Kostiantyn Kostiuk
2025-07-28  9:47             ` Philippe Mathieu-Daudé
2025-07-28  9:58               ` Kostiantyn Kostiuk
2025-07-28 11:12             ` Markus Armbruster

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=87seipkif5.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yvugenfi@redhat.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 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.