From: Rob Landley <rob@landley.net>
To: Firoz Khan <firoz.khan@linaro.org>,
linux-sh@vger.kernel.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>
Cc: y2038@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, arnd@arndb.de,
deepa.kernel@gmail.com, marcin.juszkiewicz@linaro.org
Subject: Re: [PATCH v3 0/3] sh: system call table generation support
Date: Sun, 18 Nov 2018 23:25:21 -0600 [thread overview]
Message-ID: <0b9aaa2f-9eda-82f1-8d52-b537a8c0c190@landley.net> (raw)
In-Reply-To: <1542169930-24118-1-git-send-email-firoz.khan@linaro.org>
On 11/13/18 10:32 PM, Firoz Khan wrote:
> The purpose of this patch series is, we can easily
> add/modify/delete system call table support by cha-
> nging entry in syscall.tbl file instead of manually
> changing many files. The other goal is to unify the
> system call table generation support implementation
> across all the architectures.
I applied the patch in https://github.com/landley/mkroot and the result booted
under qemu-system-sh4, seems to work fine. Network's fine, it can read a block
device, etc.
Acked-and-or-tested-by: Rob Landley <rob@landley.net>
I assume that this is just git du jour and not your patch:
WARNING: CPU: 0 PID: 1 at mm/slub.c:2448 ___slab_alloc.constprop.34+0x196/0x288
CPU: 0 PID: 1 Comm: swapper Not tainted 4.20.0-rc3 #1
PC is at ___slab_alloc.constprop.34+0x196/0x288
PR is at __slab_alloc.constprop.33+0x2a/0x4c
PC : 8c09d09a SP : 8f829ea0 SR : 400080f0
TEA : c0001240
R0 : 8c09cf04 R1 : 8c01cbec R2 : 00000000 R3 : 00000000
R4 : 8f8020a0 R5 : 006080c0 R6 : 8c01d74a R7 : 8fff5180
R8 : 8c011a40 R9 : 8fff5180 R10 : 8f8020a0 R11 : 00008000
R12 : 8c01d74a R13 : 006080c0 R14 : 8f80211c
MACH: 0000008e MACL: 0ae4849d GBR : 00000000 PR : 8c09d1b6
Call trace:
[<(ptrval)>] arch_local_irq_restore+0x0/0x24
[<(ptrval)>] __slab_alloc.constprop.33+0x2a/0x4c
[<(ptrval)>] arch_local_save_flags+0x0/0x8
[<(ptrval)>] arch_local_irq_restore+0x0/0x24
[<(ptrval)>] mm_init.isra.6+0xca/0x120
[<(ptrval)>] kmem_cache_alloc+0x9a/0xf4
[<(ptrval)>] mm_init.isra.6+0xca/0x120
[<(ptrval)>] arch_local_irq_restore+0x0/0x24
[<(ptrval)>] kmem_cache_alloc+0x9a/0xf4
[<(ptrval)>] mm_alloc+0xe/0x48
[<(ptrval)>] mm_init.isra.6+0xca/0x120
[<(ptrval)>] memset+0x0/0x8c
[<(ptrval)>] __do_execve_file+0x1de/0x574
[<(ptrval)>] getname_kernel+0x1e/0xc8
[<(ptrval)>] kmem_cache_alloc+0x0/0xf4
[<(ptrval)>] do_execve+0x16/0x24
[<(ptrval)>] arch_local_save_flags+0x0/0x8
[<(ptrval)>] arch_local_irq_restore+0x0/0x24
[<(ptrval)>] printk+0x0/0x24
[<(ptrval)>] kernel_init+0x34/0xec
[<(ptrval)>] ret_from_kernel_thread+0xc/0x14
[<(ptrval)>] schedule_tail+0x0/0x58
[<(ptrval)>] kernel_init+0x0/0xec
---[ end trace 6e84d1e05051e55d ]---
next prev parent reply other threads:[~2018-11-19 5:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 4:32 [PATCH v3 0/3] sh: system call table generation support Firoz Khan
2018-11-14 4:32 ` [PATCH v3 1/3] sh: add __NR_syscalls along with NR_syscalls Firoz Khan
2018-11-19 16:50 ` Arnd Bergmann
2018-11-20 7:05 ` Firoz Khan
2018-11-14 4:32 ` [PATCH v3 2/3] sh: add system call table generation support Firoz Khan
2018-11-14 4:32 ` [PATCH v3 3/3] sh: generate uapi header and syscall table header files Firoz Khan
2018-11-19 5:08 ` [PATCH v3 0/3] sh: system call table generation support Firoz Khan
2018-12-10 20:30 ` Rich Felker
2018-11-19 5:25 ` Rob Landley [this message]
2018-11-19 8:08 ` Geert Uytterhoeven
2018-11-19 8:57 ` Rob Landley
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=0b9aaa2f-9eda-82f1-8d52-b537a8c0c190@landley.net \
--to=rob@landley.net \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.org \
--cc=ysato@users.sourceforge.jp \
/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).