From: Steve Longerbeam <stevel@mvista.com>
To: Andi Kleen <ak@suse.de>
Cc: Hugh Dickins <hugh@veritas.com>, linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG in shared_policy_replace() ?
Date: Wed, 19 Jan 2005 10:22:45 -0800 [thread overview]
Message-ID: <41EEA575.9040007@mvista.com> (raw)
In-Reply-To: <20050119174506.GH7445@wotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
Andi Kleen wrote:
>>got it, except that there is no "new2 = NULL;" in 2.6.10-mm2!
>>
>>Looks like it was misplaced, because I do see it now in 2.6.10.
>>
>>
>
>I double checked 2.6.10 and the code also looks correct me,
>working as described by Hugh.
>
>Optimistic locking can be ugly :)
>
>
yeah, 2.6.10 makes sense to me too. But I'm working in -mm2, and
the new2 = NULL line is missing, hence my initial confusion. Trivial
patch to -mm2 attached. Just want to make sure it has been, or will be,
put back in.
Steve
[-- Attachment #2: mempolicy-mm2.diff --]
[-- Type: text/plain, Size: 253 bytes --]
--- mm/mempolicy.c.orig 2005-01-19 09:52:47.153910873 -0800
+++ mm/mempolicy.c 2005-01-19 09:53:21.548999628 -0800
@@ -1041,6 +1041,7 @@
}
n->end = start;
sp_insert(sp, new2);
+ new2 = NULL;
break;
} else
n->end = start;
next prev parent reply other threads:[~2005-01-19 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 0:31 Steve Longerbeam
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 [this message]
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=41EEA575.9040007@mvista.com \
--to=stevel@mvista.com \
--cc=ak@suse.de \
--cc=hugh@veritas.com \
--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