all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Robert Obkircher" <r.obkircher@proxmox.com>
Cc: pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup 2/2] pbs-tape: rename `buffer` to `header`
Date: Fri, 07 Aug 2026 14:52:26 +0200	[thread overview]
Message-ID: <DKIQ53OS7Z01.8X1Z9E8M3SJT@proxmox.com> (raw)
In-Reply-To: <178601383145.99099.10335181077951352838.b4-review@b4>

On Thu Aug 6, 2026 at 12:57 PM CEST, Robert Obkircher wrote:
> > ... since `BlockHeader` is now a smart pointer.
> >
> > Signed-off-by: Max R. Carrara <m.carrara@proxmox.com>
> >
> > diff --git a/pbs-tape/src/blocked_reader.rs b/pbs-tape/src/blocked_reader.rs
> > index 33c5db780..9ad16c91f 100644
> > --- a/pbs-tape/src/blocked_reader.rs
> > +++ b/pbs-tape/src/blocked_reader.rs
> > @@ -18,7 +18,7 @@ use crate::{
> >  /// the end of the stream).
> >  pub struct BlockedReader<R> {
> >      reader: R,
> > -    buffer: BlockHeader,
> > +    header: BlockHeader,
>
> I'm confused about the naming. Shouldn't this be something more like
> `buffer: BlockBuffer` which then consists of a few header fields plus a
> payload? Or is the payload really part of the header?

AFAIU the `BlockHeader` struct refers to an entire block of data written
to / read from tape (header + payload) -- so I think it's overall a bit
of a misnomer, yes.

That being said, I don't mind renaming this (and its related structs) as
part of a different series, perhaps including an overall cleanup as
well, where applicable.




  reply	other threads:[~2026-08-07 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 14:16 [PATCH proxmox-backup 0/2] Fix Undefined Behavior in Tape Block Header Deallocation Max R. Carrara
2026-08-05 14:16 ` [PATCH proxmox-backup 1/2] pbs-tape: fix undefined behavior in block header deallocation Max R. Carrara
2026-08-06 10:57   ` Robert Obkircher
2026-08-07 12:47     ` Max R. Carrara
2026-08-10  8:34       ` Robert Obkircher
2026-08-10  9:51         ` Max R. Carrara
2026-08-10 12:39           ` Robert Obkircher
2026-08-05 14:16 ` [PATCH proxmox-backup 2/2] pbs-tape: rename `buffer` to `header` Max R. Carrara
2026-08-06 10:57   ` Robert Obkircher
2026-08-07 12:52     ` Max R. Carrara [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-05 14:13 [PATCH proxmox-backup 0/2] Fix Undefined Behavior in Tape Block Header Deallocation Max R. Carrara
2026-08-05 14:13 ` [PATCH proxmox-backup 2/2] pbs-tape: rename `buffer` to `header` Max R. Carrara

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=DKIQ53OS7Z01.8X1Z9E8M3SJT@proxmox.com \
    --to=m.carrara@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=r.obkircher@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal