From: James Manning <jmm@computer.org>
To: linux-mm@kvack.org
Subject: redundant BAD_RANGE check?
Date: Tue, 20 Jun 2000 02:27:52 -0400 [thread overview]
Message-ID: <20000620022752.A2246@bp6.sublogic.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 117 bytes --]
Given that expand() appears to do its own BAD_RANGE check, it looks
unnecessary to check it again in rmqueue.
James
[-- Attachment #2: bad_range.diff --]
[-- Type: text/plain, Size: 322 bytes --]
--- linux-2.4.0-test1-ac22/mm/page_alloc.c.orig Tue Jun 20 02:24:20 2000
+++ linux-2.4.0-test1-ac22/mm/page_alloc.c Tue Jun 20 02:25:42 2000
@@ -203,8 +203,6 @@
spin_unlock_irqrestore(&zone->lock, flags);
set_page_count(page, 1);
- if (BAD_RANGE(zone,page))
- BUG();
return page;
}
curr_order++;
reply other threads:[~2000-06-20 6:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000620022752.A2246@bp6.sublogic.lan \
--to=jmm@computer.org \
--cc=linux-mm@kvack.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