Confusion in the usage of linux key management APIs

2013-03-22 Thread Ranjan Sinha
Hi, I need to store some crypto keys in the kernel where each key is related to a path on the disk. A restricted set of users can create files on such a path but the crypto keys are shared by all such user. I am thinking of using linux kernel key management facilities for my project. I have a

Re: Stackable file systems and NFS

2012-08-16 Thread Ranjan Sinha
the correct data. In addition, we cannot force specific mount options in actual deployment scenarios. edit On Tue, Aug 14, 2012 at 5:10 PM, Ranjan Sinha rnjn.si...@gmail.com wrote: For now, /etc/export file has the following setting *(rw,sync,no_root_squash) hm, AFAIK that means synchronous

Re: Stackable file systems and NFS

2012-08-16 Thread Ranjan Sinha
as the other NFS client is continuously writing to that file. -- Ranjan -Rajat On Thu, Aug 16, 2012 at 12:01 PM, Ranjan Sinha rnjn.si...@gmail.com wrote: Hi, On Tue, Aug 14, 2012 at 4:19 PM, Rajat Sharma fs.ra...@gmail.com wrote: Try mounting with noac nfs mount option to disable attribute caching

Re: Stackable file systems and NFS

2012-08-16 Thread Ranjan Sinha
On Thu, Aug 16, 2012 at 1:33 PM, Rajat Sharma fs.ra...@gmail.com wrote: What is the pattern other NFS client is writing to the file? Can't it be a legitimate NUL by any chance? Redirected output of ping. On Thu, Aug 16, 2012 at 1:22 PM, Ranjan Sinha rnjn.si...@gmail.com wrote: On Thu, Aug

Re: Stackable file systems and NFS

2012-08-14 Thread Ranjan Sinha
Hi Mulyadi, On Tue, Aug 14, 2012 at 3:33 PM, Mulyadi Santosa mulyadi.sant...@gmail.com wrote: Hi Ranjan... On Tue, Aug 14, 2012 at 2:53 PM, Ranjan Sinha rnjn.si...@gmail.com wrote: Hi, We are writing a stackable file system. While testing this on NFS we came across a situation where

Using GDB for debugging netlink communication

2012-07-21 Thread Ranjan Sinha
Hi, I have a multi-threaded application that communicates with a kernel module using netlink sockets. One of the threads in user mode application works as a server and kernel module works as a client. Roughly the kernel code is as follows:

task struct and the #! operator

2012-05-30 Thread Ranjan Sinha
Hi, I am trying to understand process creation and associated bookkeeping.I am currently trying to understand how interpreted scripts (the shebang operator) are executed. It was surprising to see that the comm member of task_struct (accessed through get_task_comm) is actually set to the name of