From: apgo@patchbomb.org (Arthur Othieno)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
apgo@patchbomb.org, linuxppc64-dev@ozlabs.org,
Paul Mackerras <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
trond.myklebust@fys.uio.no
Subject: Re: [PATCH] Fix compile for CONFIG_SYSVIPC=n or CONFIG_SYSCTL=n
Date: Mon, 20 Feb 2006 08:53:15 -0500 [thread overview]
Message-ID: <20060220135315.GA24943@krypton> (raw)
In-Reply-To: <20060220153226.30ee4b13.sfr@canb.auug.org.au>
On Mon, Feb 20, 2006 at 03:32:26PM +1100, Stephen Rothwell wrote:
> The compat syscalls are added to sys_ni.c since they are not defined
> if the above CONFIG options are off. Also, nfs would not build with
> CONFIG_SYSCTL off.
>
> Noticed by Arthur Othieno.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Looks good, thanks ;-)
Acked-by: Arthur Othieno <apgo@patchbomb.org>
> ---
>
> include/linux/nfs_fs.h | 2 +-
> kernel/sys_ni.c | 2 ++
> 2 files changed, 3 insertions(+), 1 deletions(-)
>
> On Sun, 19 Feb 2006 22:52:31 +1100 Paul Mackerras <paulus@samba.org> wrote:
> >
> > Arthur Othieno writes:
> >
> > > --- a/arch/powerpc/kernel/sys_ppc32.c
> > > +++ b/arch/powerpc/kernel/sys_ppc32.c
> > > @@ -440,7 +440,13 @@ long compat_sys_ipc(u32 call, u32 first,
> > >
> > > return -ENOSYS;
> > > }
> > > -#endif
> > > +#else
> > > +long compat_sys_ipc(u32 call, u32 first, u32 second, u32 third, compat_uptr_t ptr,
> > > + u32 fifth)
> > > +{
> > > + return -ENOSYS;
> > > +}
> > > +#endif /* CONFIG_SYSVIPC */
> >
> > Can't we just add a couple of cond_syscall lines to kernel/sys_ni.c
> > instead?
>
> Linus, can we have this applied for 2.6.16. It presumably affects sparc64
> (at least for CONFIG_SYSVIPC) as well as powerpc. The NFS fix would
> affect all architectures, I think?
>
> This has been compile tested with the CONFIG options on and off for powerpc.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
> c1a27bc400a1412c7c758775bb695e8b98d1c0c3
> diff --git a/include/linux/nfs_fs.h b/include/linux/nfs_fs.h
> index 547d649..b4dc6e2 100644
> --- a/include/linux/nfs_fs.h
> +++ b/include/linux/nfs_fs.h
> @@ -398,7 +398,7 @@ extern struct inode_operations nfs_symli
> extern int nfs_register_sysctl(void);
> extern void nfs_unregister_sysctl(void);
> #else
> -#define nfs_register_sysctl() do { } while(0)
> +#define nfs_register_sysctl() 0
> #define nfs_unregister_sysctl() do { } while(0)
> #endif
>
> diff --git a/kernel/sys_ni.c b/kernel/sys_ni.c
> index 17313b9..1067090 100644
> --- a/kernel/sys_ni.c
> +++ b/kernel/sys_ni.c
> @@ -104,6 +104,8 @@ cond_syscall(sys_setreuid16);
> cond_syscall(sys_setuid16);
> cond_syscall(sys_vm86old);
> cond_syscall(sys_vm86);
> +cond_syscall(compat_sys_ipc);
> +cond_syscall(compat_sys_sysctl);
>
> /* arch-specific weak syscall entries */
> cond_syscall(sys_pciconfig_read);
> --
> 1.2.1
prev parent reply other threads:[~2006-02-20 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060218100849.GA1869@krypton>
[not found] ` <17400.23551.904754.47979@cargo.ozlabs.ibm.com>
2006-02-20 4:32 ` [PATCH] Fix compile for CONFIG_SYSVIPC=n or CONFIG_SYSCTL=n Stephen Rothwell
2006-02-20 13:53 ` Arthur Othieno [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=20060220135315.GA24943@krypton \
--to=apgo@patchbomb.org \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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