From: Thomas Neumann <tneumann@users.sourceforge.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, xfs-masters@oss.sgi.com,
Christoph Hellwig <hch@lst.de>
Subject: Re: deadlock with fallocate
Date: Sun, 11 Oct 2009 10:53:56 +0200 [thread overview]
Message-ID: <200910111053.57159.tneumann@users.sourceforge.net> (raw)
In-Reply-To: <20091011005746.56cd3cd4.akpm@linux-foundation.org>
> 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
next prev parent reply other threads:[~2009-10-11 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 3:00 deadlock with fallocate Thomas Neumann
2009-10-11 7:57 ` Andrew Morton
2009-10-11 8:53 ` Thomas Neumann [this message]
2009-10-11 12:17 ` Christoph Hellwig
2009-10-11 14:19 ` Thomas Neumann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910111053.57159.tneumann@users.sourceforge.net \
--to=tneumann@users.sourceforge.net \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs-masters@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox