Yes there are issues. For example, sys_read and sys_write expect to receive a user virtual address for the read/write buffer. If you call these from the kernel with a kernel virtual address, you'll get an EFAULT error. If you find a solution to this problem, I would like to know it. > -----Original Message----- > From: Rajeev Bector [mailto:rajeev_bector@yahoo.com] > Sent: Friday, September 07, 2001 11:38 AM > To: kernelnewbies@nl.linux.org > Subject: FW: Question about kernel threads > > > Please CC me on this one since I am not subscribed to the list. > Thanks ! > > > Hi, > I have a simple question about kernel threads. Can they > open and close files just like user level processes ? > (by using sys_open()) etc. directly ? Are there any > side issues that we need to be aware about when doing that ? > > I have a userlevel library (that client programs will link with > to get access to a kernel module) and there is a requirement > that other kernel modules (using kernel threads) wants to > use the same library to get access to other kernel module. > So I am having to port the library to work in kernel space. > (since the library opens and closes certain device drivers, I > am wondering if that'll work seemlessly from kernel space) > > Thanks in advance for your answers ! > > regards, > Rajeev > > > > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > > > > - > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > IRC Channel: irc.openprojects.net / #kernelnewbies > Web Page: http://www.kernelnewbies.org/ > - Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ IRC Channel: irc.openprojects.net / #kernelnewbies Web Page: http://www.kernelnewbies.org/
