From: Randy Dunlap <rdunlap@xenotime.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
David Rientjes <rientjes@google.com>
Subject: Re: mmotm 2010-02-03-20-09 uploaded (mmap.c)
Date: Thu, 04 Feb 2010 12:03:01 -0800 [thread overview]
Message-ID: <4B6B27F5.6090504@xenotime.net> (raw)
In-Reply-To: <20100204105827.2270aff0.akpm@linux-foundation.org>
On 02/04/10 10:58, Andrew Morton wrote:
> On Thu, 04 Feb 2010 10:14:55 -0800
> Randy Dunlap<rdunlap@xenotime.net> wrote:
>
>> On 02/03/10 20:09, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2010-02-03-20-09 has been uploaded to
>>>
>>> http://userweb.kernel.org/~akpm/mmotm/
>>>
>>> and will soon be available at
>>>
>>> git://zen-kernel.org/kernel/mmotm.git
>>>
>>> It contains the following patches against 2.6.33-rc6:
>>
>>
>> In some config cases, this patch seems to have a problem:
>> sysctl-clean-up-vm-related-variable-declarations.patch
>>
>> In mm/mmap.c:
>> +#ifdef HAVE_ARCH_PICK_MMAP_LAYOUT
>> +/* Used by each architecture's private code and sysctl. */
>> +int sysctl_legacy_va_layout;
>> +#endif
>>
>> mm/mmap.c:92: error: expected identifier or '(' before numeric constant
>>
>> I guess that sometimes sysctl_legacy_va_layout is a #define:
>> from include/linux/mm.h:
>>
>> #ifdef CONFIG_SYSCTL
>> extern int sysctl_legacy_va_layout;
>> #else
>> #define sysctl_legacy_va_layout 0
>> #endif
>>
>> and indeed the failing builds do not have CONFIG_SYSCTL enabled.
>
> Thanks. This, I guess:
>
> --- a/mm/mmap.c~sysctl-clean-up-vm-related-variable-declarations-fix
> +++ a/mm/mmap.c
> @@ -87,7 +87,7 @@ int sysctl_overcommit_ratio = 50; /* def
> int sysctl_max_map_count __read_mostly = DEFAULT_MAX_MAP_COUNT;
> struct percpu_counter vm_committed_as;
>
> -#ifdef HAVE_ARCH_PICK_MMAP_LAYOUT
> +#if defined(HAVE_ARCH_PICK_MMAP_LAYOUT)&& defined(CONFIG_SYSCTL)
> /* Used by each architecture's private code and sysctl. */
> int sysctl_legacy_va_layout;
> #endif
> _
>
Yep, that works. Thanks.
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
--
~Randy
prev parent reply other threads:[~2010-02-04 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 4:09 mmotm 2010-02-03-20-09 uploaded akpm
2010-02-04 18:14 ` mmotm 2010-02-03-20-09 uploaded (mmap.c) Randy Dunlap
2010-02-04 18:58 ` Andrew Morton
2010-02-04 20:03 ` Randy Dunlap [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=4B6B27F5.6090504@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
/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
Powered by JetHome