In Linux host: Run the container in privileged mode (–privileged) Add all capabilities (–cap-add=ALL) mount host /lib/modules into the container (-v /lib/modules:/lib/modules) docker run –name container_name \ –privileged \ –cap-add=ALL -d \ -v /dev:/dev \ -v /lib/modules:/lib/modules \ image_id Caution: Here all Linux capabilities are added so capabilities can be refined. Few words about Linux … Read more
Can I ask why are you trying to open a file? I like to follow Linux development (out of curiosity, I’m not a kernel developer, I do Java), and I’ve seen discussion of this question before. I was able to find a LKML message about this, basically mentioning it’s usually a bad idea. I’m almost … Read more
Sometimes printk may defer output (that is, message is stored in the internal buffer, but not in kernel log). To avoid such behavior, always add newline (\n) at the end of the string printed: printk(KERN_ALERT “%s\n” ,mystring);
Don’t call SYS_readlink – use the same method that procfs does when one of those links is read. Start with the code in proc_pid_readlink() and proc_fd_link() in fs/proc/base.c. Broadly, given an int fd and a struct files_struct *files from the task you’re interested in (which you have taken a reference to), you want to do: … Read more
You should be aware that you should avoid file I/O from within Linux kernel when possible. The main idea is to go “one level deeper” and call VFS level functions instead of the syscall handler directly: Includes: #include <linux/fs.h> #include <asm/segment.h> #include <asm/uaccess.h> #include <linux/buffer_head.h> Opening a file (similar to open): struct file *file_open(const char … Read more