From: Andrew Morton <akpm@digeo.com>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.50: floppy/buffer related oops
Date: Mon, 02 Dec 2002 18:35:44 -0800 [thread overview]
Message-ID: <3DEC1880.722745C6@digeo.com> (raw)
In-Reply-To: <20021203021133.GD617@zip.com.au>
CaT wrote:
>
> I was dding to a floppy disc that had errors on it.
> ...
> buffer layer error at fs/buffer.c:2641
> Pass this trace through ksymoops for reporting
> Call Trace:
> [<c0143c03>] __buffer_error+0x33/0x38
That's not an oops. It's a debug warning.
You had non-uptodate buffers against an uptodate page. This
is an absurdity, but is not harmful.
Clearing BH_Uptodate on a write error has always seemed weird.
The error handling needs a review/rethink. Meanwhile I'll drop
a buffer_req test into those warnings to shut them up.
prev parent reply other threads:[~2002-12-03 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 2:11 CaT
2002-12-03 2:18 ` CaT
2002-12-03 2:35 ` Andrew Morton [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=3DEC1880.722745C6@digeo.com \
--to=akpm@digeo.com \
--cc=cat@zip.com.au \
--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
Powered by JetHome