public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
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: Fri, 20 Aug 2004 08:18:40 +1000	[thread overview]
Message-ID: <41252740.50401@torque.net> (raw)
In-Reply-To: <1092932342.2378.430.camel@mulgrave>

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.

James,
[Wearing my smartmontools maintainer hat] such a change is going
to cause a lot of noise in the log from the smartd daemon.
The code to use SG_IO ioctl in smartmontools is in CVS but
won't be released for a month or so.

If they are not going to be dropped in the lk 2.6 series
why not wait until the lk 2.7 development starts (or late
lk 2.6 series)?

Doug Gilbert

  parent reply	other threads:[~2004-08-19 22:19 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
2004-08-19 22:18 ` Douglas Gilbert [this message]
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=41252740.50401@torque.net \
    --to=dougg@torque.net \
    --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