From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>,
Steffen Winterfeldt <snwint@suse.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: SuSE hwinfo/yast2 still confusing SYM53C8XX, killing tape backups
Date: Fri, 03 Dec 2004 23:35:08 +0100 [thread overview]
Message-ID: <m3brdbc8o3.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <20041122133014.GF25636@parcelfarce.linux.theplanet.co.uk> (Matthew Wilcox's message of "Mon, 22 Nov 2004 13:30:14 +0000")
Matthew Wilcox <matthew@wil.cx> writes:
>> 2. is it a kernel bug if reading offset #216 (byte-wise) in the config
>> file in sysfs confuses the hardware?
>
> No, but it does seem to me that we could do better. Unfortunately,
> the obvious thing to do (set the file size to less than 256 bytes) isn't
> really possible in sysfs. But we could use the 'undocumented feature'
> in drivers/pci/pci-sysfs.c:pci_read_config() of setting the pci_dev's
> cfg_size to 128 bytes. This would prevent even root from reading more
> than 128 bytes. That'd be OK -- there's no *PCI* data in this range,
> even on the latest 1010/1030 controllers. The operating registers are
> exposed in the 0x80-0xFF range only up to the 875; the 876 and later
> return only 0 in that range.
Have you had a look at this already? If not, how would I go about
inplementing this?
--
Matthias Andree
next prev parent reply other threads:[~2004-12-03 22:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 21:20 [BK PATCH] SCSI -rc1 fixes James Bottomley
2004-11-14 23:05 ` Jeff Garzik
2004-11-14 23:09 ` James Bottomley
2004-11-14 23:54 ` Matthias Andree
2004-11-15 0:04 ` James Bottomley
2004-11-15 1:09 ` SuSE hwinfo/yast2 still confusing SYM53C8XX, killing tape backups (was: [BK PATCH] SCSI -rc1 fixes) Matthias Andree
2004-11-22 10:35 ` Steffen Winterfeldt
2004-11-22 11:17 ` Jens Axboe
2004-11-22 11:21 ` Steffen Winterfeldt
2004-11-22 11:23 ` Jens Axboe
2004-11-22 11:33 ` Steffen Winterfeldt
2004-11-22 11:37 ` Jens Axboe
2004-11-22 12:02 ` SuSE hwinfo/yast2 still confusing SYM53C8XX, killing tape backups Matthias Andree
2004-11-22 13:05 ` Steffen Winterfeldt
2004-11-22 13:30 ` Matthew Wilcox
2004-11-22 14:05 ` Matthias Andree
2004-11-26 14:16 ` Steffen Winterfeldt
2004-11-27 0:40 ` Matthias Andree
2004-11-29 11:16 ` Steffen Winterfeldt
2004-11-29 11:24 ` Matthias Andree
2004-12-03 22:35 ` Matthias Andree [this message]
2004-11-22 12:06 ` Douglas Gilbert
2004-11-22 13:07 ` Steffen Winterfeldt
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=m3brdbc8o3.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.de \
--cc=James.Bottomley@SteelEye.com \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=snwint@suse.de \
/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.