Hmm…I suppose not. I’d would still be curious what the right way to do this is, though? I think I can get away with that trick, but I can also imagine scenarios where I’d want the kernel module itself to create the file.
Thanks, Nick > On Jul 30, 2015, at 5:00 PM, [email protected] wrote: > > On Thu, 30 Jul 2015 16:03:51 -0700, Nicholas Murphy said: > >> Yes, I’ve read all the disclaimers against accessing files in the kernel, but >> I want to set up a shared memory segment between a kernel module and one or >> more user processes, and /dev/shm seems like a good way to do that. > > Is there a specific reason you aren't letting the userspace program create > an mmap() area and then write the identifying information to a /sys attribute > file (or other means of notifying the kernel of what to use)? _______________________________________________ Kernelnewbies mailing list [email protected] http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
