From: Steve Longerbeam <stevel@mvista.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: BUG in shared_policy_replace() ?
Date: Tue, 18 Jan 2005 16:31:42 -0800 [thread overview]
Message-ID: <41EDAA6E.5000900@mvista.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 125 bytes --]
Hi Andi,
Why free the shared policy created to split up an old
policy that spans the whole new range? Ie, see patch.
Steve
[-- Attachment #2: mempolicy.diff --]
[-- Type: text/plain, Size: 297 bytes --]
--- mm/mempolicy.c.orig 2005-01-18 16:13:35.573273351 -0800
+++ mm/mempolicy.c 2005-01-18 16:24:23.940608135 -0800
@@ -1052,10 +1052,6 @@
if (new)
sp_insert(sp, new);
spin_unlock(&sp->lock);
- if (new2) {
- mpol_free(new2->policy);
- kmem_cache_free(sn_cache, new2);
- }
return 0;
}
next reply other threads:[~2005-01-19 0:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 0:31 Steve Longerbeam [this message]
2005-01-19 12:37 ` Hugh Dickins
2005-01-19 17:32 ` Steve Longerbeam
2005-01-19 17:45 ` Andi Kleen
2005-01-19 18:22 ` Steve Longerbeam
2005-01-19 18:34 ` Andi Kleen
2005-01-19 18:59 ` Steve Longerbeam
2005-01-19 19:09 ` Andi Kleen
2005-01-19 19:25 ` Steve Longerbeam
2005-01-19 19:29 ` Andi Kleen
2005-01-19 21:39 ` Andrew Morton
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=41EDAA6E.5000900@mvista.com \
--to=stevel@mvista.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.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