From: Andries Brouwer <aebr@win.tue.nl>
To: Jan Kasprzak <kas@informatics.muni.cz>
Cc: linux-kernel@vger.kernel.org, hch@infradead.org,
marcelo@conectiva.com.br
Subject: Re: 2.4.20-pre11 /proc/partitions read
Date: Tue, 22 Oct 2002 20:40:34 +0200 [thread overview]
Message-ID: <20021022184034.GA26585@win.tue.nl> (raw)
In-Reply-To: <20021022161957.N26402@fi.muni.cz>
On Tue, Oct 22, 2002 at 04:19:57PM +0200, Jan Kasprzak wrote:
> I.e. if you read the /proc/partitions in single read() call,
> it gets read OK. However, if you read() with smaller-sized blocks,
> you get the truncated contents.
Having statistics in /proc/partitions leads to such problems.
Make sure you do not ask for them.
--- Documentation/Configure.help~ Mon Oct 14 01:12:13 2002
+++ Documentation/Configure.help Tue Oct 22 20:30:39 2002
@@ -561,6 +561,8 @@
This is required for the full functionality of sar(8) and interesting
if you want to do performance tuning, by tweaking the elevator, e.g.
+ On the other hand, it will cause random and mysterious failures for
+ fdisk, mount and other programs reading /proc/partitions.
If unsure, say N.
(this is about CONFIG_BLK_STATS).
Andries
[I still do not understand how hch can want to add this cruft to
/proc/partitions, and how marcelo can accept it.
If some vendor made this mistake, why force it on the rest of
the world? It is bad for RedHat users, and worse for all others.]
next prev parent reply other threads:[~2002-10-22 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 14:19 2.4.20-pre11 /proc/partitions read Jan Kasprzak
2002-10-22 15:10 ` Richard B. Johnson
2002-10-22 16:14 ` Jan Kasprzak
2002-10-22 18:40 ` Andries Brouwer [this message]
2002-10-22 18:10 ` Marcelo Tosatti
2002-10-23 8:36 ` Jan Kasprzak
2002-10-22 18:45 ` Christoph Hellwig
2002-10-22 18:59 ` Andries Brouwer
2002-10-22 18:26 ` Marcelo Tosatti
2002-10-22 19:32 ` Andries Brouwer
2002-10-22 19:35 ` Christoph Hellwig
2002-10-22 19:58 ` Andries Brouwer
2002-10-22 20:32 ` Alan Cox
2002-10-23 8:39 ` Jan Kasprzak
2002-10-23 9:13 ` Jan Kasprzak
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=20021022184034.GA26585@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=hch@infradead.org \
--cc=kas@informatics.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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