public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] get the kernel to warn about deprecated SCSI ioctls
Date: Thu, 19 Aug 2004 12:41:34 -0400	[thread overview]
Message-ID: <4124D83E.3000201@pobox.com> (raw)
In-Reply-To: <1092932940.2025.463.camel@mulgrave>

James Bottomley wrote:
> On Thu, 2004-08-19 at 12:23, Jeff Garzik wrote:
> 
>>On Thu, Aug 19, 2004 at 12:19:01PM -0400, James Bottomley wrote:
>>
>>>The non unique SCSI ioctls:
>>>
>>>SCSI_IOCTL_SEND_COMMAND
>>>SCSI_IOCTL_TEST_UNIT_READY
>>>SCSI_IOCTL_BENCHMARK_COMMAND
>>>SCSI_IOCTL_SYNC
>>>SCSI_IOCTL_START_UNIT
>>>SCSI_IOCTL_STOP_UNIT
>>>
>>>Have been deprecated for a while now.  We should make the kernel
>>>complain when a program actually uses one of them, so users have had
>>>adequate warning before they are removed.
>>
>>any chance of deprecating the doorlock ioctls too?
> 
> 
> The doorlock ones are unique, and are used by some of the CD tools.
> 
> We really need to know when an app locks the door rather than having to
> scan the commands in SG_IO.


You need to scan the commands in SG_IO anyway, otherwise you do not know 
in all cases when an app locks the door :)

	Jeff



  reply	other threads:[~2004-08-19 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 16:19 [PATCH] get the kernel to warn about deprecated SCSI ioctls James Bottomley
2004-08-19 16:21 ` Christoph Hellwig
2004-08-19 21:06   ` James Bottomley
2004-08-19 16:23 ` Jeff Garzik
2004-08-19 16:28   ` James Bottomley
2004-08-19 16:41     ` Jeff Garzik [this message]
2004-08-19 22:18 ` Douglas Gilbert
2004-08-19 22:27   ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2004-08-19 17:06 Pat LaVarre

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=4124D83E.3000201@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.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