From: Firoz Khan <firoz.khan@linaro.org>
To: "David S . Miller" <davem@davemloft.net>
Cc: sparclinux <sparclinux@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Re: [PATCH v2 3/4] sparc: add system call table generation support
Date: Fri, 2 Nov 2018 11:09:57 +0530 [thread overview]
Message-ID: <CALxhOnieTqFzs-D9mNB5nL0=iPGFE92Gwm-Coft7D0_7RJgHiQ@mail.gmail.com> (raw)
In-Reply-To: <20181101.133315.47887636039827313.davem@davemloft.net>
Hi David,
On Fri, 2 Nov 2018 at 02:03, David Miller <davem@davemloft.net> wrote:
>
> From: Firoz Khan <firoz.khan@linaro.org>
> Date: Thu, 1 Nov 2018 19:23:10 +0530
>
> > +141 common getpeername sys_getpeername sys_nis_syscall
> ...
> > +150 common getsockname sys_getsockname sys_nis_syscall
>
> The sys_nis_syscall in these two entries is incorrect, see the patch
> below.
True, The patch you mentioned here is the merged recently and I
created this patch series
few hours before that.
>
> One of my worst fears about this change has been realized, that
> instead of helping us find problems, it is so automated to the point
> that it fails to question issues like this.
Yes. I have created the system call table generation support for 10
architecture including
sparc. Every architecture I validated the generated file with replaced
one and made sure
both are same. But still I expect some human errors. The one which I
missed was caught
by respective maintainers.
BTW, the error can be raised only one time, during the development.
> If sys_nis_syscall for the compat syscall shows up in a situation where the
> native 32-bit syscall does have an entry, that's a BUG and the script should
> point this out so that the bug can be fixed.
syscall.tbl is the input to the script, so the developers has the
responsibility to fill the table
properly. I don't know, we have to write a script which has to be
smart enough to catch the
wrong syscall entries.
Thanks for your feedback.
Firoz
>
> Thank you.
>
> ====================
> From 1f2b5b8e2df4591fbca430aff9c5a072dcc0f408 Mon Sep 17 00:00:00 2001
> From: "David S. Miller" <davem@davemloft.net>
> Date: Wed, 31 Oct 2018 18:30:21 -0700
> Subject: [PATCH] sparc64: Wire up compat getpeername and getsockname.
>
> Fixes: 8b30ca73b7cc ("sparc: Add all necessary direct socket system calls.")
> Reported-by: Joseph Myers <joseph@codesourcery.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
> arch/sparc/kernel/systbls_64.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/sparc/kernel/systbls_64.S b/arch/sparc/kernel/systbls_64.S
> index bb68c80..ff9389a 100644
> --- a/arch/sparc/kernel/systbls_64.S
> +++ b/arch/sparc/kernel/systbls_64.S
> @@ -47,9 +47,9 @@ sys_call_table32:
> .word sys_recvfrom, sys_setreuid16, sys_setregid16, sys_rename, compat_sys_truncate
> /*130*/ .word compat_sys_ftruncate, sys_flock, compat_sys_lstat64, sys_sendto, sys_shutdown
> .word sys_socketpair, sys_mkdir, sys_rmdir, compat_sys_utimes, compat_sys_stat64
> -/*140*/ .word sys_sendfile64, sys_nis_syscall, compat_sys_futex, sys_gettid, compat_sys_getrlimit
> +/*140*/ .word sys_sendfile64, sys_getpeername, compat_sys_futex, sys_gettid, compat_sys_getrlimit
> .word compat_sys_setrlimit, sys_pivot_root, sys_prctl, sys_pciconfig_read, sys_pciconfig_write
> -/*150*/ .word sys_nis_syscall, sys_inotify_init, sys_inotify_add_watch, sys_poll, sys_getdents64
> +/*150*/ .word sys_getsockname, sys_inotify_init, sys_inotify_add_watch, sys_poll, sys_getdents64
> .word compat_sys_fcntl64, sys_inotify_rm_watch, compat_sys_statfs, compat_sys_fstatfs, sys_oldumount
> /*160*/ .word compat_sys_sched_setaffinity, compat_sys_sched_getaffinity, sys_getdomainname, sys_setdomainname, sys_nis_syscall
> .word sys_quotactl, sys_set_tid_address, compat_sys_mount, compat_sys_ustat, sys_setxattr
> --
> 2.1.2.532.g19b5d50
>
next prev parent reply other threads:[~2018-11-02 5:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 13:53 [PATCH v2 0/4] sparc: system call table generation support Firoz Khan
2018-11-01 13:53 ` [PATCH v2 1/4] sparc: move __IGNORE* entries to non uapi header Firoz Khan
2018-11-01 13:53 ` [PATCH v2 2/4] sparc: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-11-01 13:53 ` [PATCH v2 3/4] sparc: add system call table generation support Firoz Khan
2018-11-01 20:33 ` David Miller
2018-11-02 5:39 ` Firoz Khan [this message]
2018-11-02 6:04 ` David Miller
2018-11-05 10:48 ` Arnd Bergmann
2018-11-06 4:28 ` David Miller
2018-11-01 13:53 ` [PATCH v2 4/4] sparc: generate uapi header and system call table files Firoz Khan
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='CALxhOnieTqFzs-D9mNB5nL0=iPGFE92Gwm-Coft7D0_7RJgHiQ@mail.gmail.com' \
--to=firoz.khan@linaro.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=deepa.kernel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
/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).