From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] tape: mam: actually enforcing the length when writing attributes
Date: Fri, 24 May 2024 09:50:05 +0200 [thread overview]
Message-ID: <0917bf6a-8207-44ec-b5c2-718e20c23fd2@proxmox.com> (raw)
In-Reply-To: <20240523100800.3969965-1-d.csapak@proxmox.com>
Am 23/05/2024 um 12:08 schrieb Dominik Csapak:
> we have to check against the length of the attribute, not the u16
> maximum value.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> pbs-tape/src/sg_tape/mam.rs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/pbs-tape/src/sg_tape/mam.rs b/pbs-tape/src/sg_tape/mam.rs
> index 4e995d0b..dc5163a5 100644
> --- a/pbs-tape/src/sg_tape/mam.rs
> +++ b/pbs-tape/src/sg_tape/mam.rs
> @@ -169,7 +169,7 @@ pub fn write_mam_attribute<F: AsRawFd>(
> attr_data.extend(data);
> if !data.is_empty() && data.len() < attribute.len as usize {
> attr_data.resize(attr_data.len() - data.len() + attribute.len as usize, 0);
> - } else if data.len() > u16::MAX as usize {
> + } else if data.len() > attribute.len as usize {
> bail!("data to long");
Can we extend this error with the attribute name, the length we got and
the defined max length to have some more info for when a user runs into
this?
Something like:
bail!("attribute '{}' length {} is over the maximum allowed length {}", ...);
Or is this error already extended/concatenated with similar info somewhere
in the return chain (sorry, just doing a quick review directly in my MUA)
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-05-24 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 10:08 Dominik Csapak
2024-05-24 7:50 ` Thomas Lamprecht [this message]
2024-05-24 8:19 ` Dominik Csapak
2024-05-24 8:26 ` Thomas Lamprecht
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=0917bf6a-8207-44ec-b5c2-718e20c23fd2@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-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