[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090224144800.4c7e3fcb.akpm@linux-foundation.org>
Date: Tue, 24 Feb 2009 14:48:00 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alexey Dobriyan <adobriyan@...il.com>
Cc: serue@...ibm.com, clg@...ibm.com, linux-kernel@...r.kernel.org,
containers@...ts.osdl.org
Subject: Re: [PATCH 4/4] mqueue namespace: adapt sysctl
On Wed, 25 Feb 2009 01:32:45 +0300
Alexey Dobriyan <adobriyan@...il.com> wrote:
> > > +proc_handler *proc_mq_dointvec = NULL;
> > > +proc_handler *proc_mq_dointvec_minmax = NULL;
> > > +#endif
> >
> > looks odd. Was this
> >
> > --- a/ipc/mq_sysctl.c~mqueue-namespace-adapt-sysctl-update-fix
> > +++ a/ipc/mq_sysctl.c
> > @@ -52,8 +52,8 @@ static int proc_mq_dointvec_minmax(ctl_t
> > lenp, ppos);
> > }
> > #else
> > -proc_handler *proc_mq_dointvec = NULL;
> > -proc_handler *proc_mq_dointvec_minmax = NULL;
> > +#define proc_mq_dointvec NULL
> > +#define proc_mq_dointvec_minmax NULL
> > #endif
>
> I hope, not.
>
> "#define foo NULL" is the least intrusive thing.
well the original code would have spat a warning at compile time
then tried to execute code from BSS at runtime, methinks.
But I can't be assed working out how to disable CONFIG_SYSCTL to
test that. Gawd I hate `select'.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists