From: David Woodhouse <dwmw2@infradead.org>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: free_list / free_size messages
Date: Tue, 16 Mar 2004 08:11:25 +0000 [thread overview]
Message-ID: <1079424685.5835.404.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <405686B3.4090607@wasp.net.au>
On Tue, 2004-03-16 at 08:46 +0400, Brad Campbell wrote:
> I have seen this a bit on my iPAQ 3800 with a familiar 2.4.19-hh36 kernel. I just guessed it was
> informative and I tend to ignore it. Should I try and reproduce it for debugging?
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.
--
dwmw2
next prev parent reply other threads:[~2004-03-16 8:11 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 [this message]
2004-03-17 17:32 ` Brian T
2004-03-17 17:35 ` David Woodhouse
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=1079424685.5835.404.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=brad@wasp.net.au \
--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