From: Christoph Hellwig <hch@infradead.org>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Jann Horn <jannh@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] SCSI fixes for 4.18-rc3
Date: Tue, 10 Jul 2018 23:45:42 -0700 [thread overview]
Message-ID: <20180711064542.GA7377@infradead.org> (raw)
In-Reply-To: <70d566f0-2dda-60c2-7c7a-e09e371f8607@cybernetics.com>
On Tue, Jul 10, 2018 at 05:53:18PM -0400, Tony Battersby wrote:
> At my job (https://www.cybernetics.com/), I use the write()/read()
> interface to the SCSI generic driver for access to tape drives and tape
> medium changers. For example, the write()/read() interface is useful
> for implementing RAID-like functionality for tape drives since a single
> thread can send commands to multiple tape drives at once and poll() for
> command completion. We have a lot of code invested in this interface,
> so it would be a huge pain for us if it were removed. But in our case,
> everything runs as root (as the firmware of an embedded storage
> appliance), so extra permission checks should be OK.
Do you just use read/write on /dev/sg or also on /dev/bsg? Because
I started a discussion to kill the read/write support for the latter
even before Linus brought it up here.. (and we have the same fix
pending for /dev/bsg)
next prev parent reply other threads:[~2018-07-11 6:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 21:38 [GIT PULL] SCSI fixes for 4.18-rc3 James Bottomley
2018-07-07 2:31 ` Linus Torvalds
2018-07-07 2:39 ` Linus Torvalds
2018-07-07 2:48 ` Linus Torvalds
2018-07-07 5:22 ` James Bottomley
2018-07-10 0:41 ` Linus Torvalds
2018-07-10 17:36 ` Jann Horn
2018-07-10 17:49 ` Linus Torvalds
2018-07-10 18:04 ` Linus Torvalds
2018-07-10 21:53 ` Tony Battersby
2018-07-10 22:24 ` Linus Torvalds
2018-07-11 0:40 ` Linus Torvalds
2018-07-11 6:45 ` Christoph Hellwig [this message]
2018-07-11 13:56 ` Tony Battersby
2018-07-16 16:20 ` Jann Horn
2018-07-07 3:08 ` Jann Horn
2018-07-07 3:25 ` Linus Torvalds
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=20180711064542.GA7377@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tonyb@cybernetics.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).