Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
From:   Dror Levin <drorl@infinidat.com>
Date:   Sun, 2 Sep 2018 14:35:53 +0300
Message-ID: <CAOuWhkaGjX8Q_xghkFVTqzZkDrUv-sdH=VbS7hvnqFWrT+3eOQ@mail.gmail.com>
Subject: Recent removal of bsg read/write support
To:     linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Note: I am not subscribed to LKML so please CC replies to this email.

Hi,

We have an internal tool that uses the bsg read/write interface to
issue SCSI commands as part of a test suite for a storage device.

After recently reading on LWN that this interface is to be removed we
tried porting our code to use sg instead. However, that raises new
issues - mainly getting ENOMEM over iSCSI for unknown reasons.

Because of this we would like to continue using the bsg interface,
even if some changes are required to meet security concerns.

Is there any chance for this removal to be reverted? I saw it was
already included in 4.19-rc1.

Regards,
Dror