From: Christoph Lameter <cl@linux.com>
To: Pekka Enberg <penberg@iki.fi>
Cc: paulmck@linux.vnet.ibm.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, penberg@kernel.org,
mpm@selenic.com
Subject: Re: Memory allocator semantics
Date: Mon, 10 Feb 2014 13:07:58 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.10.1402101304110.17517@nuc> (raw)
In-Reply-To: <52F60699.8010204@iki.fi>
On Sat, 8 Feb 2014, Pekka Enberg wrote:
> So to be completely honest, I don't understand what is the race in (A) that
> concerns the *memory allocator*. I also don't what the memory allocator can
> do in (B) and (C) which look like double-free and use-after-free,
> respectively, to me. :-)
Well it seems to be some academic mind game to me.
Does an invocation of the allocator have barrier semantics or not?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-02-10 19:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 20:33 Paul E. McKenney
2014-01-03 3:39 ` Josh Triplett
2014-01-03 5:14 ` Paul E. McKenney
2014-01-03 5:47 ` Josh Triplett
2014-01-03 7:57 ` Paul E. McKenney
2014-01-03 8:42 ` Josh Triplett
2014-02-08 10:27 ` Pekka Enberg
2014-02-09 2:00 ` Paul E. McKenney
2014-02-11 8:50 ` Pekka Enberg
2014-02-11 12:09 ` Paul E. McKenney
2014-02-11 18:43 ` Christoph Lameter
2014-02-14 17:30 ` Paul E. McKenney
2014-02-10 19:07 ` Christoph Lameter [this message]
2014-02-11 12:14 ` Paul E. McKenney
2014-02-11 13:20 ` Pekka Enberg
2014-02-11 15:01 ` Paul E. McKenney
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=alpine.DEB.2.10.1402101304110.17517@nuc \
--to=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@iki.fi \
--cc=penberg@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