All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] [ARM] implement arch_randomize_brk()
Date: Fri, 18 Jun 2010 13:15:52 +0100	[thread overview]
Message-ID: <20100618121552.GA19044@shareable.org> (raw)
In-Reply-To: <4C1B50AA.9050507@ru.mvista.com>

Sergei Shtylyov wrote:
> >+extern unsigned long arch_randomize_brk(struct mm_struct *mm);
> >+#define arch_randomize_brk arch_randomize_brk
> 
>    Isn't this an "infinitely recursive" macro?

Not in ISO C.  It'll expand to itself and stop.  This is a handy trick
for confirming #ifdef tests elsewhere.  Glibc does it a lot for enums
defined in header files, for those which applications commonly test
with #ifdef because they were traditionally defined using macros.

-- Jamie

  reply	other threads:[~2010-06-18 12:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 20:33 [PATCH 0/5] enablement of some security features missing on ARM Nicolas Pitre
2010-06-16 20:33 ` [PATCH 1/5] [ARM] implement arch_randomize_brk() Nicolas Pitre
2010-06-18 10:55   ` Sergei Shtylyov
2010-06-18 12:15     ` Jamie Lokier [this message]
2010-06-16 20:33 ` [PATCH 2/5] [ARM] add address randomization to mmap() Nicolas Pitre
2010-06-16 23:42   ` Kyungmin Park
2010-06-17  0:05     ` Nicolas Pitre
2010-06-17  0:25       ` Kyungmin Park
2010-06-16 20:33 ` [PATCH 3/5] ARM: initial stack protector (-fstack-protector) support Nicolas Pitre
2010-06-16 20:33 ` [PATCH 4/5] ARM: stack protector: change the canary value per task Nicolas Pitre
2010-06-16 20:33 ` [PATCH 5/5] Stack protector: test module Nicolas Pitre

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=20100618121552.GA19044@shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-arm-kernel@lists.infradead.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.