Le Thu, 6 Dec 2007 16:18:24 +0530,
"Sandeep K Sinha" <[EMAIL PROTECTED]> a écrit :
> Am I logically wrong somewhere ??
Yes, you should not open files from the kernel:
http://kernelnewbies.org/FAQ/WhyWritingFilesFromKernelIsBad
Thomas
--
Thomas Petazzoni, [EMAIL PROTECTED], http://thomas.enix.o
Oops... I had missed the setting of fs to the oldfs...
Thanks.
On Dec 7, 2007 1:29 PM, Vivek Kutal <[EMAIL PROTECTED]> wrote:
> Sandeep K Sinha wrote:
> > It returns with ENOENT after using set_fs.
> >
> >
> same code works for me.
> take a look at this http://www.linuxjournal.com/article/8110
> t
Sandeep K Sinha wrote:
It returns with ENOENT after using set_fs.
same code works for me.
take a look at this http://www.linuxjournal.com/article/8110
there is a example given at the end.
HTH
--
Vivek Kutal
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies
On Thu, 6 Dec 2007 18:37:06 +0530
"Sandeep K Sinha" <[EMAIL PROTECTED]> wrote:
> It returns with ENOENT after using set_fs.
Why do you need to do a sys_open from kernel?
system calls are for user space i guess.
You are already in kernel.
how about using sysfs interface and passing info to a file
It returns with ENOENT after using set_fs.
On Dec 6, 2007 5:11 PM, Vivek Kutal <[EMAIL PROTECTED]> wrote:
> Sandeep K Sinha wrote:
> > Well, I am trying to write a kernel module which when inserted should
> > created a file foo at any absolute location.
> > This is a code snippet of the same. It r
Sandeep K Sinha wrote:
Well, I am trying to write a kernel module which when inserted should
created a file foo at any absolute location.
This is a code snippet of the same. It returns with error No -14.
This a part of the constructor code for the module. I am using 2.6.20 kernel.
char x
Hello,
On Dec 6, 2007 11:48 AM, Sandeep K Sinha <[EMAIL PROTECTED]> wrote:
> Well, I am trying to write a kernel module which when inserted should
> created a file foo at any absolute location.
> This is a code snippet of the same. It returns with error No -14.
> This a part of the constructor cod
Well, I am trying to write a kernel module which when inserted should
created a file foo at any absolute location.
This is a code snippet of the same. It returns with error No -14.
This a part of the constructor code for the module. I am using 2.6.20 kernel.
char x1[64]="/home/ssinha/foo";
