From: Maneesh Soni <maneesh@in.ibm.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>, axboe@suse.de
Subject: Re: 2.6.10-rc2-bk7 - kernel BUG at fs/sysfs/file.c:87!
Date: Wed, 24 Nov 2004 14:41:38 -0600 [thread overview]
Message-ID: <20041124204138.GA2543@in.ibm.com> (raw)
In-Reply-To: <002c01c4d25b$3e8b9b10$0201a8c0@hawk>
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.
Maneesh
--
Maneesh Soni
Linux Technology Center,
IBM Austin
email: maneesh@in.ibm.com
Phone: 1-512-838-1896 Fax:
T/L : 6781896
next prev parent reply other threads:[~2004-11-24 20:44 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 [this message]
2004-11-24 21:18 ` Jens Axboe
2004-11-24 21:32 ` Greg KH
2004-11-25 6:58 ` Jens Axboe
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=20041124204138.GA2543@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=axboe@suse.de \
--cc=caker@theshore.net \
--cc=greg@kroah.com \
--cc=linux-kernel@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