Fix inittab back to adding /proc, fops sketch, scripts to automate debugfs

This commit is contained in:
Ciro Santilli
2017-05-12 17:06:34 +01:00
parent 401666d221
commit 2f77a45f63
6 changed files with 44 additions and 14 deletions

View File

@@ -1,17 +1,11 @@
/*
Adapted from: https://github.com/chadversary/debugfs-tutorial/blob/47b3cf7ca47208c61ccb51b27aac6f9f932bfe0b/example1/debugfs_example1.c
Requires CONFIG_DEBUG_FS.
Usage:
mkdir /debugfs
mount -t debugfs none /debugfs
insmod /debugfs.ko
cd /debugfs/kernel_module_cheat
cat myfile
/debugfs.sh
Output:
42
Requires `CONFIG_DEBUG_FS=y`.
*/
#include <linux/debugfs.h>

View File

@@ -1,6 +1,10 @@
/*
dmesg stuff when fops happen.
Usage:
/fops.sh
fops define what the kernel will do on filesystem system calls on all of
/dev, /proc, /sys, and consistute the main method of userland communication
in drivers (syscalls being the other one).
@@ -19,19 +23,19 @@ static struct dentry *dir = 0;
int fop_open(struct inode *inode, struct file *file)
{
printk(KERN_INFO "open");
printk(KERN_INFO "open\n");
return 0;
}
ssize_t fop_read(struct file *file, char __user *buf, size_t len, loff_t *off)
{
printk(KERN_INFO "read");
printk(KERN_INFO "read\n");
return 0;
}
ssize_t fop_write(struct file *file, const char __user *buf, size_t len, loff_t *off)
{
printk(KERN_INFO "write");
printk(KERN_INFO "write\n");
return 0;
}
@@ -41,7 +45,7 @@ http://stackoverflow.com/questions/11393674/why-is-the-close-function-is-called-
*/
int fop_release (struct inode *inode, struct file *file)
{
printk(KERN_INFO "release");
printk(KERN_INFO "release\n");
return 0;
}