From: Johannes Weiner <hannes@cmpxchg.org>
To: Tejun Heo <tj@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
hpa@zytor.com, mingo@redhat.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/percpu] bootmem: clean up arch-specific bootmem wrapping
Date: Wed, 25 Feb 2009 03:43:16 +0100 [thread overview]
Message-ID: <20090225024316.GA1738@cmpxchg.org> (raw)
In-Reply-To: <49A4ACAE.4020104@kernel.org>
On Wed, Feb 25, 2009 at 11:27:58AM +0900, Tejun Heo wrote:
> Hello,
>
> Johannes Weiner wrote:
> > No, when the patch was submitted for review, I pointed out the change
> > in semantics and gathered from Tejun's reaction that this wasn't done
> > intentionally. So the problem is the change itself, not the missing
> > declaration.
>
> Yeah, I should have regenerated the tree. Sorry about that.
Sorry about my rude way of commenting.
> >>>From the original mail:
> >
> > Johannes Weiner wrote:
> > > This won't suffice as reserve_bootmem() doesn't use
> > > alloc_bootmem_core(), so now you effectively removed the
> > > node-0 restriction for reserve_bootmem() on this
> > > configuration.
> >
> > Ah... right. :-(
> >
> > I just wrote again because I didn't understand why Tejun acknowledged
> > the error in the patch and then it went into -tip anyway.
> >
> > The other part of my email was just suggestions for a cleanup, I
> > wasn't referring to that when I said 'broken' - sorry if that is how
> > it came over.
>
> It seems that the wrapping thing was broken both before and after the
> patch and can lead to panic on free path. I'll soon post a patch to
> fix it.
Ok, thanks for looking into it!
Hannes
next prev parent reply other threads:[~2009-02-25 2:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-c132937556f56ee4b831ef4b23f1846e05fde102@kernel.org>
2009-02-24 21:46 ` [tip:core/percpu] bootmem: clean up arch-specific bootmem wrapping Johannes Weiner
2009-02-24 21:49 ` Ingo Molnar
2009-02-24 23:49 ` Johannes Weiner
2009-02-25 2:27 ` Tejun Heo
2009-02-25 2:43 ` Johannes Weiner [this message]
2009-02-25 4:52 ` Tejun Heo
2009-02-25 4:53 ` Tejun Heo
2009-02-27 2:58 ` Tejun Heo
2009-02-27 8:16 ` Johannes Weiner
2009-02-25 12:51 ` Ingo Molnar
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=20090225024316.GA1738@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.