XFS Developers, Ok here is what I have done: I have a tree that already had XFS 1.1 (with a bunch of other stuff) included. I hand applied the XFS 1.2 on top of XFS 1.1 patch and everything seems to
the preempt patch is applied (heavily modified, as I said :) however, I have preemption turned off. The other significant difference is the use of the real time scheduler (which is also turned off).
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 p
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.
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. -steve Christoph Hellwig wrote: On
If possible get kbd into your tree. Then open a bug and attach what ever backtraces you can get. bta is a good place to start. That might shed some light on the situation, but without wading through
XFS Developers, Ok here is what I have done: I have a tree that already had XFS 1.1 (with a bunch of other stuff) included. I hand applied the XFS 1.2 on top of XFS 1.1 patch and everything seems to
the preempt patch is applied (heavily modified, as I said :) however, I have preemption turned off. The other significant difference is the use of the real time scheduler (which is also turned off).
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 p
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.
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. -steve Christoph Hellwig wrote: On
If possible get kbd into your tree. Then open a bug and attach what ever backtraces you can get. bta is a good place to start. That might shed some light on the situation, but without wading through