From: Arnd Bergmann <arnd@arndb.de>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Sachin P Sant <sachinp@linux.vnet.ibm.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Address Sparse Static Warning inside kernel/fork.c
Date: Thu, 6 Aug 2009 19:22:34 +0200 [thread overview]
Message-ID: <200908061922.34515.arnd@arndb.de> (raw)
In-Reply-To: <20090806170600.32631.77680.sendpatchset@subratamodak.linux.ibm.com>
On Thursday 06 August 2009, Subrata Modak wrote:
> --- a/kernel/fork.c 2009-08-05 12:00:51.000000000 +0530
> +++ b/kernel/fork.c 2009-08-06 22:26:30.000000000 +0530
> @@ -78,7 +78,7 @@
> unsigned long total_forks; /* Handle normal Linux uptimes. */
> int nr_threads; /* The idle threads do not count.. */
>
> -int max_threads; /* tunable limit on nr_threads */
> +static int max_threads; /* tunable limit on nr_threads */
>
> DEFINE_PER_CPU(unsigned long, process_counts) = 0;
>
> @@ -168,7 +168,7 @@ void __put_task_struct(struct task_struc
> #define arch_task_cache_init()
> #endif
>
> -void __init fork_init(unsigned long mempages)
> +static void __init fork_init(unsigned long mempages)
> {
> #ifndef __HAVE_ARCH_TASK_STRUCT_ALLOCATOR
> #ifndef ARCH_MIN_TASKALIGN
These are both wrong (you didn't try compiling the kernel with
that patch, did you?):
fork_init() is called from init/main.c, max_threads is accessed
in kernel/sysctl.c.
If you had tried building this, you would have seen a warning about
unused symbols in the compile stage, followed by a linker error.
I would still be good to address these two though. Please do a
patch that moves the extern declarations for these two symbols
to an appropriate header file that is included in fork.c.
Arnd <><
prev parent reply other threads:[~2009-08-06 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 17:06 [PATCH] Address Sparse Static Warning inside kernel/fork.c Subrata Modak
2009-08-06 17:22 ` Arnd Bergmann [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=200908061922.34515.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sachinp@linux.vnet.ibm.com \
--cc=subrata@linux.vnet.ibm.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