From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
Date: Thu, 07 Apr 2005 13:21:23 +0200 [thread overview]
Message-ID: <425517B3.2010702@suse.de> (raw)
In-Reply-To: <20050407103123.GB9586@infradead.org>
Christoph Hellwig wrote:
> On Thu, Apr 07, 2005 at 11:46:27AM +0200, Hannes Reinecke wrote:
>>Hi all,
>>
>>/proc/scsi/scsi currently has a very dumb implementation of the seq_file
>>api which causes 'cat /proc/scsi/scsi' to return with -ENOMEM when a
>>large amount of devices are connected.
>
> /proc/scsi/scsi is deprecated and even only compiled in if
> "legacy /proc/scsi/ support" is enabled. Please move over to lssci which
> is using sysfs ASAP.
>
Ah. And that's enough reason for it not to work properly?
Deprecated as it may be, but one could at least expect it to _work_.
Puzzled.
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-04-07 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 9:46 [PATCH] Use proper seq_file api for /proc/scsi/scsi Hannes Reinecke
2005-04-07 10:31 ` Christoph Hellwig
2005-04-07 11:21 ` Hannes Reinecke [this message]
2005-04-07 11:24 ` Christoph Hellwig
2005-04-08 7:23 ` Jeremy Higdon
2005-04-08 7:56 ` Christoph Hellwig
2005-04-08 7:59 ` Arjan van de Ven
2005-04-08 8:10 ` Jeremy Higdon
2005-04-08 14:27 ` Christoph Hellwig
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=425517B3.2010702@suse.de \
--to=hare@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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