From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=vrJS=QZ=vger.kernel.org=linux-fsdevel-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED,
	HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT
	autolearn=ham autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 950ADC43381
	for <linux-fsdevel@archiver.kernel.org>; Mon, 18 Feb 2019 15:15:52 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id 62A76217D9
	for <linux-fsdevel@archiver.kernel.org>; Mon, 18 Feb 2019 15:15:52 +0000 (UTC)
Authentication-Results: mail.kernel.org;
	dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="R+M7Hbt1"
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1731331AbfBRPPv (ORCPT
        <rfc822;linux-fsdevel@archiver.kernel.org>);
        Mon, 18 Feb 2019 10:15:51 -0500
Received: from bombadil.infradead.org ([198.137.202.133]:60256 "EHLO
        bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1729971AbfBRPPv (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Mon, 18 Feb 2019 10:15:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
        d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version
        :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:
        Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:
        Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:
        List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
         bh=Yd673/bZsI/lWohx4acadJrVu7fDWTLz4coEY1Do5u8=; b=R+M7Hbt1DbHpvsa13LNkodA1J
        +hR4HdHvnY1WV9XWZZdcFeiAARP88JlrqFGzw7nzqksn83w0Ac/q3PyT232lGxzXgbhzCDTRLpUln
        JCvruj/kizM0Lj96FHsMFF9IIshY7lHrECjoSkhEuxbI6akL3CRaSqTrUGfWtMWGCuck2JZQ34vxS
        onhxDsgIHn6KalBJKXZzzqislo6sy4y13wnRJ63c7EuvoEsoI+qYHsLYuom4XC+U7hKI9TDkrRlfo
        qj1lxsctR4QU7CJwReGTIGjzynKIzRgU2zxnNya1ZfgTv8RHR3t8IWTtxWlwIsDqkCJix7/MKlZyw
        tGpDOOzgg==;
Received: from willy by bombadil.infradead.org with local (Exim 4.90_1 #2 (Red Hat Linux))
        id 1gvke5-0002GP-J2; Mon, 18 Feb 2019 15:15:49 +0000
Date:   Mon, 18 Feb 2019 07:15:49 -0800
From:   Matthew Wilcox <willy@infradead.org>
To:     Adam Borowski <kilobyte@angband.pl>
Cc:     linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
        Marcin =?utf-8?Q?=C5=9Alusarz?= <marcin.slusarz@intel.com>
Subject: Re: tmpfs fails fallocate(more than DRAM)
Message-ID: <20190218151549.GS12668@bombadil.infradead.org>
References: <20190218133423.tdzawczn4yjdzjqf@angband.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190218133423.tdzawczn4yjdzjqf@angband.pl>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: linux-fsdevel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-fsdevel.vger.kernel.org>
X-Mailing-List: linux-fsdevel@vger.kernel.org

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".