All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: linux-scsi@vger.kernel.org
Subject: Re: SG_GET_ACCESS_COUNT ioctl problem
Date: Tue, 10 Jan 2006 04:50:32 -0500	[thread overview]
Message-ID: <43C38368.5040101@cfl.rr.com> (raw)
In-Reply-To: <43C37932.90006@torque.net>

Douglas Gilbert wrote:

> Mark,
> In the lk 2.6 series you can open a disk directly
> (e.g. /dev/sda) and send it SCSI commands using the
> SG_IO ioctl. The situation is the same if you open
> the corresponding sg device and send SCSI commands.
> 
> What is important is which SCSI commands are sent. There
> is some crude filtering based on file permissions and
> the SCSI command opcode. Other than that, the onus is
> on the person sending the SCSI commands. Mounted file
> systems can be seen in /proc/mounts ** .
> 
> The sg driver is a pass through. The SG_GET_ACCESS_COUNT
> ioctl was a window to a variable which someone else removed
> around 18 months ago. There is little I can do other
> than try to explain ...
> 

Understood and thanks for the info. I know about being having a limited
set of CDB opcodes available for the sd devices however it is much to
limited for me. It just doesn't make sense to me that the "window to the
variable" was closed without offerring a simple alternative.

An application that has been in use for years using a documented and
supported API now eats my root device if I run it???? I think sombody
wasn't thinking too clearly or took an easy way out to a problem they
didn't care to address.

Thanks again
Mark

  reply	other threads:[~2006-01-10  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 13:54 SG_GET_ACCESS_COUNT ioctl problem Mark Hounschell
2006-01-10  8:23 ` Douglas Gilbert
2006-01-10  8:38   ` Mark Hounschell
2006-01-10  9:06     ` Douglas Gilbert
2006-01-10  9:50       ` Mark Hounschell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-08 13:45 Mark Hounschell

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=43C38368.5040101@cfl.rr.com \
    --to=dmarkh@cfl.rr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.