so in trying to debug my problem, I instrumented the branch manipulation code a bit, this output that we can look at
addbranch: calling printputmaps at end of function printputmaps: enter putmap (0) @ f2ce0800 putmap (1) @ 00000000 putmap (2) @ f35b1aa0 putmap (3) @ f3226e40 putmap (4) @ f121bba0 putmap (5) @ f3226d80 putmap (6) @ f0a6b9a0 putmap (7) @ f1d5fb60 putmap (8) @ f1d17840 putmap (9) @ 00000000 putmap (10) @ f7216980 putmap (11) @ 00000000 putmap (12) @ f72167c0 putmap (13) @ 00000000 putmap (14) @ f7216940 putmap (15) @ 00000000 putmap (16) @ de224440 printputmaps: exit basically, the above is what the putmap table of pointers looks like at the end of addbranch. I then call --mode, so rdwr branch is called, and near the beginning it also prints it out. rdwrbranch: calling printputmaps b4 newputmap printputmaps: enter putmap (0) @ f2ce0800 putmap (1) @ 00000000 putmap (2) @ f35b1aa0 putmap (3) @ f3226e40 putmap (4) @ f121bba0 putmap (5) @ f3226d80 putmap (6) @ f0a6b9a0 putmap (7) @ f1d5fb60 putmap (8) @ f1d17840 putmap (9) @ 00000000 putmap (10) @ f7216980 putmap (11) @ 00000000 putmap (12) @ f72167c0 putmap (13) @ 00000000 putmap (14) @ f7216940 putmap (15) @ fef70000 putmap (16) @ de22443e notice, 15 has changed, and 16 has been corrupted. and then I hit an oops Unable to handle kernel paging request at virtual address fef70000 dont know how to debug this putmap code, as its very complicated. _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
