From: Jens Axboe <axboe@suse.de>
To: Greg KH <greg@kroah.com>
Cc: Maneesh Soni <maneesh@in.ibm.com>,
"Christopher S. Aker" <caker@theshore.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc2-bk7 - kernel BUG at fs/sysfs/file.c:87!
Date: Thu, 25 Nov 2004 07:58:36 +0100 [thread overview]
Message-ID: <20041125065836.GB10233@suse.de> (raw)
In-Reply-To: <20041124213231.GA3132@kroah.com>
On Wed, Nov 24 2004, Greg KH wrote:
> On Wed, Nov 24, 2004 at 10:18:00PM +0100, Jens Axboe wrote:
> > On Wed, Nov 24 2004, Maneesh Soni wrote:
> > > On Wed, Nov 24, 2004 at 07:26:43PM +0000, Christopher S. Aker wrote:
> > > > Doing "cat /sys/block/sda/queue/iosched/show_status" produces the following BUG:
> > > >
> > > > ------------[ cut here ]------------
> > > > kernel BUG at fs/sysfs/file.c:87!
> > >
> > > I think you are using cfq io scheduler. show_status is from cfq_ioched. Looks
> > > like return value freom cfq_status_show() is going beyond one page.
> > > read/write buffer for sysfs text attribute files is limited to one page.
> >
> > Yeah, with many processes that is easy to hit. I dunno how to fix it
> > yet, is it possible to combine sysfs with the seq stuff? The file should
> > just be deleted, though.
>
> sysfs files should have only 1 value per file. You really have a single
> value that is bigger than a page size? :)
It's pi with a lot of decimals :)
I know, it's a debug entry to be able to watch what is going on inside
the scheduler. Everything doesn't fit nicely into a one-value-per-file
system.
--
Jens Axboe
prev parent reply other threads:[~2004-11-25 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 19:24 2.6.10-rc2-bk7 - kernel BUG at fs/sysfs/file.c:87! Christopher S. Aker
2004-11-24 20:41 ` Maneesh Soni
2004-11-24 21:18 ` Jens Axboe
2004-11-24 21:32 ` Greg KH
2004-11-25 6:58 ` Jens Axboe [this message]
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=20041125065836.GB10233@suse.de \
--to=axboe@suse.de \
--cc=caker@theshore.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
/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