From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: applied: [PATCH] fix #7823: tape: don't set up a data-in transfer for non-data commands
Date: Tue, 22 Sep 2026 22:34:34 +0200 [thread overview]
Message-ID: <179010927039.4032217.6669723958191565211.b4-ty@b4> (raw)
In-Reply-To: <20260817123128.2813924-1-d.csapak@proxmox.com>
On Mon, 17 Aug 2026 14:29:52 +0200, Dominik Csapak wrote:
> do_command() required a transfer buffer of at least 16 bytes, so all
> commands without a data transfer phase (REWIND, SPACE, LOCATE, MOVE
> MEDIUM, ...) allocated a dummy buffer just to satisfy that check. Since
> create_scsi_pt_obj() hands any non-empty buffer to
> set_scsi_pt_data_in(), those commands announced a data-in transfer that
> they never fulfill.
>
> [...]
Applied, thanks!
[1/1] fix #7823: tape: don't set up a data-in transfer for non-data commands
commit: 308ad7fa5442051adc44c56fe1d4a1084bdcaae0
prev parent reply other threads:[~2026-09-22 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 12:29 [PATCH] fix #7823: tape: don't set up a data-in transfer for non-data commands Dominik Csapak
2026-09-22 20:34 ` Thomas Lamprecht [this message]
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=179010927039.4032217.6669723958191565211.b4-ty@b4 \
--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