This page summarizes the process of contributing code to the ext4 kernel driver or to e2fsprogs.
- Clone the e2fsprogs git repo (git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git)
- Make your code modifications as you see fit.
- Write some functional tests (see tests/ for examples, and use
make testnewto generate a new test) if you're writing new code.
- Run the regression suite:
- Wash, rinse, repeat until your code does what you want it to do.
- Static analysis, part 1: Run
make gcc-wall-newto compile with all GCC warnings enabled.
- Static analysis, part 2: Run
make clean; make C=1to check your code against sparse.
- Regression tests: Run
cd tests/; make test_script; ./test_script --valgrind-leakcheckto look for memory leaks.
- When writing up your patches, please follow the guidelines in https://www.kernel.org/doc/Documentation/SubmittingPatches
- Send patches to the mailing list linux-ext4 at vger.kernel.org.
While Eric Sandeen and Ted T'so occasionally upload code snapshots to Coverity as an additional checkpoint, these steps can be performed by any developer.
1. Clone the kernel git repo (git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) 1. https://www.kernel.org/doc/Documentation/SubmittingPatches