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 03:38:49 -0500 [thread overview]
Message-ID: <43C37299.6050301@cfl.rr.com> (raw)
In-Reply-To: <43C36EFA.1040800@torque.net>
> Mark,
> I think you can consider that ioctl deprecated in the
> lk 2.6 series. The implementation of that ioctl in
> lk 2.6.15 is not very encouraging:
>
> case SG_GET_ACCESS_COUNT:
> /* faked - we don't have a real access count anymore */
> val = (sdp->device ? 1 : 0);
> return put_user(val, ip);
>
> which will yield 1 in almost all cases. In the lk 2.6 series
> sysfs ** is meant to take over those sort of functions from
> the sg driver. However struct scsi_device (one instance per
> scsi device (normally a logical unit)) no longer seems to
> maintain an access count.
>
>
> I have written about the SG_IO ioctl and its various
> implementations in the lk 2.6 series at:
> http://www.torque.net/sg/sg_io.html
>
> However I haven't addressed the status of the lesser used
> sg ioctls (e.g. SG_GET_ACCESS_COUNT) in the lk 2.6 series.
>
>
> ** ..._GET_ACCESS_COUNT is more of a job for procfs than
> sysfs.
>
So how can one safely open an sg device that happens to be a disk? I can
find no combination of open flags that will cause an open to fail if the
disk happens to be mounted? You imply this ioctl is a "lesser used"
ioctl? What 'was' the prefered method of doing this? It's the only
method I found short of writing code to xlate the sg device into an sd
device and attempting an open of that first. That's not good???
Thanks
Mark
next prev parent reply other threads:[~2006-01-10 8:38 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 [this message]
2006-01-10 9:06 ` Douglas Gilbert
2006-01-10 9:50 ` Mark Hounschell
-- 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=43C37299.6050301@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.