From: Christoph Egger <siccegge@cs.fau.de>
To: Alessandro Zummo <a.zummo@towertech.it>,
Paul Gortmaker <p_gortmaker@yahoo.com>,
Andrew Morton <akpm@linux-foundation.org>,
maltesch@gmx.de, Ralf Baechle <ralf@linux-mips.org>,
Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org
Cc: vamos@i4.informatik.uni-erlangen.de
Subject: Re: [PATCH] Un(de)selectable block for DISCONTIGMEM/64BIT on parisc
Date: Wed, 12 May 2010 17:45:16 +0200 [thread overview]
Message-ID: <20100512154516.GB722@faui48a.informatik.uni-erlangen.de> (raw)
In-Reply-To: <20100512153229.GA3379@faui49.informatik.uni-erlangen.de>
Hi all!
Seems I messed up the logic a bit -- reading the ifndef for an
ifdef reversing the actual behaviour of the code when applying the
patch. Below the corrected variant.
Regards
Christoph
On Wed, May 12, 2010 at 05:32:29PM +0200, Christoph Egger wrote:
> Hi all!
>
> As part of the VAMOS[0] research project at the University of
> Erlangen we are looking at multiple integrity errors in linux'
> configuration system.
>
> When considering the restrictions inposed in kconfig 64BIT
> will *always* be set when DISCONTIGMEM is present on parisc so the
> code path depending on !64BIT is actually unreachable and the whole
> check unnecessary.
>
> Please keep me informed of this patch getting confirmed /
> merged so we can keep track of it.
>
> Regards
>
> Christoph Egger
>
> [0] http://vamos1.informatik.uni-erlangen.de/
----
>From 5eeae9c56e2602a68b62b21691e6756fb5198dd7 Mon Sep 17 00:00:00 2001
From: Christoph Egger <siccegge@cs.fau.de>
Date: Wed, 12 May 2010 16:59:24 +0200
Subject: [PATCH] on parisc CONFIG_DISCONTIGMEM always depends on CONFIG_64BIT
Removing a conditional on 64BIT inside a DISCONTIGMEM block inside
arch/parisc. DISCONTIGMEM depends on ARCH_DISCONTIGMEM_ENABLE either
directly or through DISCONTIGMEM_MANUAL which in turn depends on 64BIT
inside Kconfig so the check and the else case isn't needed at all (the
else case can't ever be reached)
Signed-off-by: Christoph Egger <siccegge@cs.fau.de>
---
arch/parisc/include/asm/mmzone.h | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/arch/parisc/include/asm/mmzone.h b/arch/parisc/include/asm/mmzone.h
index 9608d2c..dbddcac 100644
--- a/arch/parisc/include/asm/mmzone.h
+++ b/arch/parisc/include/asm/mmzone.h
@@ -35,12 +35,8 @@ extern struct node_map_data node_data[];
#define PFNNID_MAP_MAX 512 /* support 512GB */
extern unsigned char pfnnid_map[PFNNID_MAP_MAX];
-#ifndef CONFIG_64BIT
-#define pfn_is_io(pfn) ((pfn & (0xf0000000UL >> PAGE_SHIFT)) == (0xf0000000UL >> PAGE_SHIFT))
-#else
/* io can be 0xf0f0f0f0f0xxxxxx or 0xfffffffff0000000 */
#define pfn_is_io(pfn) ((pfn & (0xf000000000000000UL >> PAGE_SHIFT)) == (0xf000000000000000UL >> PAGE_SHIFT))
-#endif
static inline int pfn_to_nid(unsigned long pfn)
{
--
1.6.3.3
prev parent reply other threads:[~2010-05-12 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 15:32 [PATCH] Un(de)selectable block for DISCONTIGMEM/64BIT on parisc Christoph Egger
2010-05-12 15:45 ` Christoph Egger [this message]
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=20100512154516.GB722@faui48a.informatik.uni-erlangen.de \
--to=siccegge@cs.fau.de \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=herton@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=maltesch@gmx.de \
--cc=p_gortmaker@yahoo.com \
--cc=ralf@linux-mips.org \
--cc=rtc-linux@googlegroups.com \
--cc=vamos@i4.informatik.uni-erlangen.de \
/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;
as well as URLs for NNTP newsgroup(s).