From: Andries.Brouwer@cwi.nl
To: linux-kernel@vger.kernel.org
Subject: mm and Oops
Date: Wed, 27 Jun 2001 04:32:16 +0200 (MET DST) [thread overview]
Message-ID: <UTC200106270232.EAA456067.aeb@vlet.cwi.nl> (raw)
After sending util-linux out, I booted a kernel that had kdev_t
a pointer type, to see whether that still works.
And all (minus md/lvm/nfs that didnt compile) was fine
except that kswapd produced an oops. Investigation shows
that it was caused by the combination of what <linux/swap.h> calls
"Ugly ugly ugly HACK" and what <linux/kdev_t.h> judges with "yuk".
So, maybe we must remove one or both of these sore spots.
The second one is the use of a special constant B_FREE
as device value to indicate that the buffer is free.
I'll look at this tomorrow but perhaps someone knows:
must the constant B_FREE (used only in fs/buffer.c) be nonzero?
If so, then we probably need a bitfield to indicate "free".
Otherwise we can use 0 ("no device") as value.
Andries
next reply other threads:[~2001-06-27 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 2:32 Andries.Brouwer [this message]
2001-06-27 8:15 ` Andreas Dilger
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=UTC200106270232.EAA456067.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--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
all inboxes | Powered by JetHome®