On 12/03/2014 02:06 AM, Dave Airlie wrote:
On 2 December 2014 at 21:59, Thomas Hellstrom thellstrom@vmware.com wrote:
Kernel side fence objects are used when unbinding resources and may thus be created as part of a memory reclaim operation. This might trigger recursive memory reclaims and result in the kernel running out of stack space.
So a simple way out is to avoid accounting of these fence objects. In principle this is OK since while user-space can trigger the creation of such objects, it can't really hold on to them. However, their lifetime is quite long, so some form of accounting should perhaps be implemented in the future.
Fixes kernel crashes when running, for example viewperf11 ensight-04 test 3 with low system memory settings.
are these 3 intended for fixes? can you send me a git pull for them soon, so they don't miss Linus release.
Dave.
Hi.
Actually, these bugs have been quite long-standing and I feel a bit uncomfortable including the fixes this late in the release cycle. I'd rather wait to 3.19 unless you think otherwise.
Thanks, Thomas