Theodore Ts'o b6e96d0067 jbd2: use module parameters instead of debugfs for jbd_debug ... There are multiple reasons to move away from debugfs. First of all, we are only using it for a single parameter, and it is much more complicated to set up (some 30 lines of code compared to 3), and one more thing that might fail while loading the jbd2 module. Secondly, as a module paramter it can be specified as a boot option if jbd2 is built into the kernel, or as a parameter when the module is loaded, and it can also be manipulated dynamically under /sys/module/jbd2/parameters/jbd2_debug. So it is more flexible. Ultimately we want to move away from using jbd_debug() towards tracepoints, but for now this is still a useful simplification of the code base. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>		2013-02-09 16:29:20 -05:00
..
checkpoint.c
commit.c	jbd2: track request delay statistics	2013-02-06 22:30:23 -05:00
journal.c	jbd2: use module parameters instead of debugfs for jbd_debug	2013-02-09 16:29:20 -05:00
Kconfig	jbd2: Grab a reference to the crc32c driver if necessary	2012-05-27 07:50:56 -04:00
Makefile
recovery.c	jbd2: check return value of blkdev_issue_flush()	2012-08-17 09:56:17 -04:00
revoke.c	jbd2: checksum revocation blocks	2012-05-27 08:08:24 -04:00
transaction.c	jbd2: add tracepoints which provide per-handle statistics	2013-02-08 13:00:22 -05:00