I understand filesystem code quite well, and the particular problem (if
you would have read the oops) is in the memory management layer. But
thanks for your advice.|
Christoph Hellwig wrote:
On Tue, Mar 25, 2003 at 01:32:50PM -0700, Steven Dake wrote:
I suspect the issue wouldn't present itself with a vanilla 2.4.18 +
xfs1.2 tree as it would have already been caught... And unfortunately I
can't apply to a plain vanilla tree, it must go into this particular
tree for my company to release it...
If you have any suggestions on how I could debug, I'd be willing to try
I was really hoping someone had run into this type of problem in the
past and could provide some quick pointers on how I could debug.
Maybe get some consultant that knows Linux filesystem code to fix it for
your company? I wouldn't expect too much help on a heavily patched
tree that's not publically available.