From: Matthew Wilcox <willy@infradead.org>
To: Adam Borowski <kilobyte@angband.pl>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
"Marcin Ślusarz" <marcin.slusarz@intel.com>
Subject: Re: tmpfs fails fallocate(more than DRAM)
Date: Mon, 18 Feb 2019 07:15:49 -0800 [thread overview]
Message-ID: <20190218151549.GS12668@bombadil.infradead.org> (raw)
In-Reply-To: <20190218133423.tdzawczn4yjdzjqf@angband.pl>
On Mon, Feb 18, 2019 at 02:34:23PM +0100, Adam Borowski wrote:
> The returned error is ENOMEM rather than POSIX mandated ENOSPC (for
> posix_allocate(), but our documentation doesn't mention ENOMEM for
> Linux-specific fallocate() either).
Returning -ENOMEM rather than -ENOSPC in this situation is clearly
wrong, but just about every system call can return -ENOMEM. It might
not even be due to memory allocation failure ... these days it's just
"I am unusually short on resources, you've done nothing wrong, but I
can't handle it right now".
next prev parent reply other threads:[~2019-02-18 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 13:34 tmpfs fails fallocate(more than DRAM) Adam Borowski
2019-02-18 15:15 ` Matthew Wilcox [this message]
2019-02-18 20:25 ` Adam Borowski
2019-02-19 3:35 ` Hugh Dickins
2019-02-19 4:16 ` Dave Chinner
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=20190218151549.GS12668@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=kilobyte@angband.pl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcin.slusarz@intel.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;
as well as URLs for NNTP newsgroup(s).