[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1283102928-3051-1-git-send-email-namhyung@gmail.com>
Date: Mon, 30 Aug 2010 02:28:45 +0900
From: Namhyung Kim <namhyung@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Phillip Lougher <phillip@...gher.demon.co.uk>,
Arnd Bergmann <arnd@...db.de>,
Al Viro <viro@...iv.linux.org.uk>, linux-kernel@...r.kernel.org
Subject: [RFC v2 PATCH 0/3] initramfs: cleanups
Hello,
This patchset tries to cleanup init/initramfs code especially for syscall
invocation which produces many warnings from sparse because of address
space change. One possible solution would be eliminating such calls at all
and use internal kernel functions directly. But Al Viro mentions there's
a historical(?) reason not to do so. [1]
First two of this patchset wrap all of syscall invocations with kern_sys_*()
helper functions which does nasty address space conversions for you. This
idea was suggested by Arnd Bergmann. Last one tries to implement above idea
- calling internel functions directly - in favour of kernel config option
even though I'm not sure this is right thing. :-(
This patchset depends on my previous patch "init: mark __user address space
on string literals" [2] now contained in -mm tree.
Any comments would be welcomed.
Thanks.
[1] http://lkml.org/lkml/2010/8/20/202
[2] http://lkml.org/lkml/2010/8/18/157
---
Namhyung Kim (3):
init: add sys-wrapper.h
initramfs: use kern_sys_* macros instead of syscall
init: introduce CONFIG_USE_INIT_SYSCALL_AS_KERNEL_ROUTINE
init/Makefile | 2 +
init/sys-wrapper.c | 589 ++++++++++++++++++++++++++++++++++++++++++++++++++++
init/sys-wrapper.h | 305 +++++++++++++++++++++++++++
usr/Kconfig | 7 +
4 files changed, 903 insertions(+), 0 deletions(-)
create mode 100644 init/sys-wrapper.c
create mode 100644 init/sys-wrapper.h
--
1.7.2.2
--
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