Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 358
  • Last Modified:

Sharing between different processes using driver

I've created a memory module that gets installed as a driver. I create a node for this module on the filesystem. Some applications open the node and write to it, while others read from it. Whenever a process writes to it, the module stores it in kernel memory, however when another process goes to read, it doesn't appear to see the same memory that was written, as if it has a separate instance of the module. How can I make it so it sees the same memory?

Code Example for the module:

char * data;

init_module
{
  data =(char *) kmalloc(100,GFP_KERNEL);
}

read(char * buf,.....)
{
  copy_to_user(buf,data,100);
}


So if "init_module" is called during the insert the module, it creates the memory space for the global variable "data", but then when process A  tries to call read, it gets a segmentation fault, as if the memory had never been allocated. Can anyone explain this?
0
stauffec
Asked:
stauffec
  • 3
  • 2
1 Solution
 
scnCommented:
Is the user space variable buf correctly allocated by the process before the call to read?
0
 
stauffecAuthor Commented:
In the code snippet up top, the initialization of the module (insmod) causes the allocation of the memory and it is successfully freed at the removal of the module (rmmod). HOwever, any other process opening the driver and trying to read or write to it seems to get a segmentation fault, as if the memory wasn't allocated. What i'm not sure of is if that allocation of memory done on the insmod call is still visible when another process tries to call read, which is supposed to read data from that memory. If it cannot see it, how can I have a module that can allow one process to write into a memory space and then have another process read from that same kernel memory. I thought the module was the bridge for that.
0
 
scnCommented:
kmalloc allocates memory into the kernel space so, while inside the module read function, any process can read this memory. Then, copy_to_user(buf,data,100) copies the "data" variable (belonging to kernel memory area) content to the buf variable (belonging to the process memory area) asuming that buf has already been allocated by the calling process.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
stauffecAuthor Commented:
OK, I understand that kmalloc allocates memory in the kernel, however, is the variable char pointer "data" that is assigned the memory allocation during module initilization the same variable that will be seen by another process when it calls the read function, or when the process opens the node and calls read, is a new variable "data" instantiated, for the process?
0
 
scnCommented:
data is the same variable. You can check it easily by putting some content to data in the init function and display it with a printk in read function. Below is a complete example:

kernel module
---------------
// includes ...
char *data;

static int my_open(struct inode *inode, struct file *file) {
      return 0;
}

static int my_release(struct inode *inode, struct file *file) {
      return 0;
}

static ssize_t my_read(struct file *file, char *buf, size_t count, loff_t *ppos){
      printk(KERN_INFO "Data values [%s]\n", data);
      copy_to_user(buf,data,100);
}

static struct file_operations my_fops = {
      owner:  THIS_MODULE,
      open:   my_open,
      release:my_release,
      read:   my_read,
};

static int __init my_init(void) {
      int ret;
  if (ret=register_chrdev(62, "/dev/mydrv", &my_fops)) {
    printk(KERN_ERR "Failed to register driver, errno %d\n", ret);
            return -1;
  }
      data = kmalloc(100, GFP_KERNEL);
      memcpy(data,"a string",9);
      return 0;
}

static void __exit my_exit(void) {
}

module_init(my_init);
module_exit(my_exit);


Process source:
-----------------
// includes ...
int main() {
      int fd,nb;
      char *buf;

      fd = open("/dev/mydrv", O_RDONLY);
      if (fd<0) {printf("OPEN error\n"); exit (0);}
      buf=(char*)malloc(100);
      nb=read(fd, buf, 100);
      if (nb<0) printf("Read error %d\n", errno);
      else      printf("Read [%s]\n", buf);
      close(fd);
}

Creation of the device node: mknod /dev/mydrv c 62 0

When executing ./u, the line "Data values [astring]" is added to /var/log/messages (if syslog configured for it) and the process displays on stdout "Read [astring]".
Hope that helps.

0
 
Anthony2000Commented:
Have you tried adding a printk after the memory is allocated to make sure that your init function is getting called? I have done what you are trying to do and had no problems.

Rubini has an example that I started with in his book on device drivers: http://www.xml.com/ldd/chapter/book/

and the examples from the book: http://examples.oreilly.com/linuxdrive2/

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now