From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Matthew Dharm <mdharm-scsi@one-eyed-alien.net>,
SCSI development list <linux-scsi@vger.kernel.org>,
USB Storage List <usb-storage@one-eyed-alien.net>
Subject: Re: Sysfs attribute file for max_sectors
Date: 06 Jan 2004 13:47:54 -0600 [thread overview]
Message-ID: <1073418475.2047.82.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0401061427230.6168-100000@ida.rowland.org>
On Tue, 2004-01-06 at 13:31, Alan Stern wrote:
> I was going to have a store() routine that would accept any value greater
> than 0 and <= the value in the host template (or SCSI_DEFAULT_MAX_SECTORS
> if the host template value is 0 -- that's what scsi_host_alloc() does).
> If this is writeable only by root, would that be acceptable for all SCSI
> devices?
Not really. For most drivers, the max_sectors is a driver table
parameter and the user shouldn't be changing it.
The value can be acceptably exported read only in scsi_sysfs.c; then,
you could use the attribute overriding code to make this read/write for
usb-storage only.
James
next prev parent reply other threads:[~2004-01-06 19:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031207051634.GB21951@one-eyed-alien.net>
2003-12-08 16:15 ` Notify about errors during initialization Alan Stern
2004-01-05 2:10 ` Matthew Dharm
2004-01-05 22:04 ` Alan Stern
2004-01-05 22:13 ` Christoph Hellwig
2004-01-05 23:32 ` Mike Anderson
2004-01-06 16:17 ` Christoph Hellwig
2004-01-06 17:15 ` Patrick Mansfield
2004-01-06 17:18 ` Christoph Hellwig
2004-01-06 18:08 ` Mike Anderson
2004-01-06 18:08 ` Christoph Hellwig
2004-01-06 19:04 ` Mike Anderson
2004-01-06 18:07 ` Sysfs attribute file for max_sectors Alan Stern
2004-01-06 18:23 ` James Bottomley
2004-01-06 19:31 ` Alan Stern
2004-01-06 19:47 ` James Bottomley [this message]
2004-01-07 16:16 ` PATCH: (as168) " Alan Stern
2004-01-06 21:11 ` Patrick Mansfield
2004-01-06 21:14 ` Jens Axboe
2004-01-06 22:00 ` Alan Stern
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=1073418475.2047.82.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=patmans@us.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@one-eyed-alien.net \
/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