From: Christoph Hellwig <hch@infradead.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Jan Kasprzak <kas@informatics.muni.cz>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre11 /proc/partitions read
Date: Tue, 22 Oct 2002 20:35:04 +0100 [thread overview]
Message-ID: <20021022203504.A7770@infradead.org> (raw)
In-Reply-To: <20021022193226.GC26585@win.tue.nl>; from aebr@win.tue.nl on Tue, Oct 22, 2002 at 09:32:26PM +0200
On Tue, Oct 22, 2002 at 09:32:26PM +0200, Andries Brouwer wrote:
> On Tue, Oct 22, 2002 at 04:26:35PM -0200, Marcelo Tosatti wrote:
>
> > > No. I do not claim that his problem was caused by the stats.
> > > It is just that I get reports from people with mysterious mount
> > > and fdisk problems that go away when CONFIG_BLK_STATS is disabled.
> >
> > Could you forward?
> >
> > Thats really bad.
>
> The best reference is
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=35980
>
> with fsck affected.
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=62414
>
> shows that mount is affected.
Both of those should be fixed by my patch, i.e. were caused by a bug
in fpos handling in the seq_file /proc/partions. There is nothing
about the statistics in them.
next prev parent reply other threads:[~2002-10-22 19:29 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
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 [this message]
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=20021022203504.A7770@infradead.org \
--to=hch@infradead.org \
--cc=aebr@win.tue.nl \
--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 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.