lkml.org 
[lkml]   [2009]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: deadlock with fallocate
Date
> Will legacy applications fail on newer kernels?  Or is it the case that
> only recently-written applications which utilise new kernel
> functionality will hit this bug?
In theory posix_fallocate has been around for a while and glibc will use
kernel functionality if available, so applications might break. In practice it
is perhaps not that common that applications use fallocate.

The problem is definitively fallocate related. When I replace possix_fallocate
with the equivalent ftruncate64 call the problem goes away. (But then again
the two calls are not really equivalent, and fallocate is the semantic that I
need).
Furthermore the deadlocks seem to start occurring after writing more data than
available main memory, but I did not investigate this thoroughly.

Thomas



\
 
 \ /
  Last update: 2009-10-11 11:15    [W:0.062 / U:2.428 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site