Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 2 Jul 2002 08:22:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 2 Jul 2002 08:22:13 -0400 Received: from sccrmhc03.attbi.com ([204.127.202.63]:26356 "EHLO sccrmhc03.attbi.com") by vger.kernel.org with ESMTP id ; Tue, 2 Jul 2002 08:22:12 -0400 Message-ID: <3D219A52.1060008@quark.didntduck.org> Date: Tue, 02 Jul 2002 08:19:30 -0400 From: Brian Gerst User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020607 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Timo Benk CC: linux-kernel Subject: Re: allocate memory in userspace References: <20020701172659.GA4431@toshiba> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 982 Lines: 28 Timo Benk wrote: > Hi, > > I am a kernel newbie and i am writing a module. I > need to allocate some memory in userspace because > i want to access syscalls like open(), lstat() etc. > I need to call these methods in the kernel, and in > my special case there is no other way, but i > do not want to reimplement all the syscalls. What are you trying to do with this module? If you are needing to use syscalls like open(), you are probably trying to do something that is forbidden in kernel space. For example, trying to read a configuration file. Recommended reading: http://www.linux.org.uk/~ajh/ols2002_proceedings.pdf.gz The chapter named "How NOT to write kernel drivers", especially sections 7 and 8. -- Brian Gerst - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/