From: David Woodhouse <dwmw2@infradead.org>
To: Brian T <btuch@usa.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: free_list / free_size messages
Date: Wed, 17 Mar 2004 17:35:10 +0000 [thread overview]
Message-ID: <1079544909.16952.92.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <011201c40c45$d318a160$fd0ba8c0@briantpc>
On Wed, 2004-03-17 at 11:32 -0600, Brian T wrote:
> >
> > Yes please. It should be harmless; it's just an accounting screwup. We
> > seem to have placed a block on the free_list which doesn't actually have
> > any significant amount of free space in it at all.
> >
> > --
>
> I am limited to my debugging output, but here is what I caught from syslog
> around the "eep".
That's not useful; we need to see what it was thinking at the time it
put it _on_ the list, not at the time it later takes it off and finds it
shouldn't have been there in the first place.
If you update to the current code, does it still happen?
--
dwmw2
prev parent reply other threads:[~2004-03-17 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 18:12 free_list / free_size messages Brian T
2004-03-15 21:28 ` Brian T
2004-03-15 21:46 ` David Woodhouse
2004-03-16 4:46 ` Brad Campbell
2004-03-16 8:11 ` David Woodhouse
2004-03-17 17:32 ` Brian T
2004-03-17 17:35 ` David Woodhouse [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=1079544909.16952.92.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=btuch@usa.net \
--cc=linux-mtd@lists.infradead.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