From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH common v4 1/2] sysfstools: file_write: extend with logging
Date: Mon, 11 Nov 2024 11:29:47 +0100 [thread overview]
Message-ID: <b8cdbf8d-a2f1-41f7-99d3-12333d14fadc@proxmox.com> (raw)
In-Reply-To: <20241111101758.1259669-2-d.csapak@proxmox.com>
Am 11.11.24 um 11:17 schrieb Dominik Csapak:
> the actual error and path is useful to know when trying to debug or
> figure out what did not work, so warn here if there was an error.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> changes from v3:
> * only add the logging in this patch, not the error ignore handling
>
> src/PVE/SysFSTools.pm | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/src/PVE/SysFSTools.pm b/src/PVE/SysFSTools.pm
> index 0bde6d7..772f6d6 100644
> --- a/src/PVE/SysFSTools.pm
> +++ b/src/PVE/SysFSTools.pm
> @@ -211,17 +211,23 @@ sub check_iommu_support{
> return PVE::Tools::dir_glob_regex('/sys/class/iommu/', "[^\.].*");
> }
>
> +# writes $buf into $filename, on success returns 1, on error returns 0 and warns
> sub file_write {
> my ($filename, $buf) = @_;
>
> my $fh = IO::File->new($filename, "w");
> return undef if !$fh;
>
> - my $res = defined(syswrite($fh, $buf)) ? 1 : 0;
> -
> + my $res = syswrite($fh, $buf);
> $fh->close();
just to be sure: and the fh->close cannot alter `$!` ?
Otherwise, we probably want to assign my $sys_err = $! before the $fh->close()
call, and maybe comment that it only is relevant if $res is not defined.
>
> - return $res;
> + if (defined($res)) {
> + return 1;
> + } elsif (my $err = $!) {
> + warn "error writing '$buf' to '$filename': $err\n";
> + }
> +
> + return 0;
> }
>
> sub pci_device_info {
Korrigieren
Schließen
Grammatik
This sentence does not start with an uppercase letter.
BeforeIgnorieren
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-11 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 10:17 [pve-devel] [PATCH common/qemu-server v4] improve sysfs write behaviour Dominik Csapak
2024-11-11 10:17 ` [pve-devel] [PATCH common v4 1/2] sysfstools: file_write: extend with logging Dominik Csapak
2024-11-11 10:29 ` Thomas Lamprecht [this message]
2024-11-11 10:32 ` Dominik Csapak
2024-11-11 10:17 ` [pve-devel] [PATCH common v4 2/2] sysfstools: fix regression on binding to vfio-pci Dominik Csapak
2024-11-11 10:17 ` [pve-devel] [PATCH qemu-server v4 1/1] pci: don't hard require resetting devices for passthrough Dominik Csapak
2024-11-11 11:06 ` [pve-devel] [PATCH common/qemu-server v4] improve sysfs write behaviour Dominik Csapak
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=b8cdbf8d-a2f1-41f7-99d3-12333d14fadc@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.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