> I wish there were a way to track down this sort of problem in a
> systematic way, other than just hoping that continued code review and
> improvement will catch the error.
Hmmm, locate the dentry list in a read-only segment, remarking it as r/w
whenever we need to manipulate its contents? Slow but thorough. Same for
buffers?
Patches like this and the memory leak tester should be (relatively hidden)
config options.
Chris