From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH common v2 1/2] sysfstools: file_write: extend with logging and ignore list
Date: Fri, 8 Nov 2024 11:24:29 +0100 [thread overview]
Message-ID: <20241108112429.27b7be35@rosa.proxmox.com> (raw)
In-Reply-To: <20241108093300.1023657-2-d.csapak@proxmox.com>
2 cosmetic nits inline:
On Fri, 8 Nov 2024 10:32:58 +0100
Dominik Csapak <d.csapak@proxmox.com> wrote:
> 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.
>
> Also takes now an optional error list that can be ignored. If
> encountering such an error, returns success instead of failure.
suggestion:
Now also takes an optional list of errors that can be ignored.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> src/PVE/SysFSTools.pm | 22 ++++++++++++++++++----
> 1 file changed, 18 insertions(+), 4 deletions(-)
>
> diff --git a/src/PVE/SysFSTools.pm b/src/PVE/SysFSTools.pm
> index 0bde6d7..156fee6 100644
> --- a/src/PVE/SysFSTools.pm
> +++ b/src/PVE/SysFSTools.pm
> @@ -211,17 +211,31 @@ sub check_iommu_support{
> return PVE::Tools::dir_glob_regex('/sys/class/iommu/', "[^\.].*");
> }
>
> +# writes $buf into $filename
> +# returns success when encountering an error from the given $ignore_list, e.g. EEXIST
I somehow read this as only condition when it returns success (also not
sure if the comment is needed or this gets clear when looking through the
code)?
maybe:
# writes $buf into $filename, returns false and warns on errors not listed in the optional $ignore_list
?
> sub file_write {
> - my ($filename, $buf) = @_;
> + my ($filename, $buf, $ignore_list) = @_;
if you do:
$ignore_list //= [];
here...
>
> 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();
>
> - return $res;
> + if (defined($res)) {
> + return 1;
> + } elsif (my $err = $!) {
> + if (defined($ignore_list)) {
.. this nesting can be omitted.
> + for my $to_ignore ($ignore_list->@*) {
> + if ($err == $to_ignore) {
> + return 1;
> + }
the inner if could be shorted a bit to:
return 1 if ($err == $to_ignore);
> + }
> + }
> + warn "error writing '$buf' to '$filename': $err\n";
> + }
> +
> + return 0;
> }
>
> sub pci_device_info {
_______________________________________________
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-08 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 9:32 [pve-devel] [PATCH common/qemu-server v2] improve sysfs write behaviour Dominik Csapak
2024-11-08 9:32 ` [pve-devel] [PATCH common v2 1/2] sysfstools: file_write: extend with logging and ignore list Dominik Csapak
2024-11-08 10:24 ` Stoiko Ivanov [this message]
2024-11-08 9:32 ` [pve-devel] [PATCH common v2 2/2] sysfstools: fix regression on binding to vfio-pci Dominik Csapak
2024-11-08 10:26 ` Stoiko Ivanov
2024-11-08 9:33 ` [pve-devel] [PATCH qemu-server v2 1/1] pci: don't hard require resetting devices for passthrough Dominik Csapak
2024-11-08 10:28 ` [pve-devel] [PATCH common/qemu-server v2] improve sysfs write behaviour Stoiko Ivanov
2024-11-11 8:13 ` 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=20241108112429.27b7be35@rosa.proxmox.com \
--to=s.ivanov@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 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.