Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2751528imm; Tue, 4 Sep 2018 09:25:40 -0700 (PDT) X-Google-Smtp-Source: ANB0Vda6wKqg2XmO7Anr9AHglRBeBHEZT1ZgPEN4VEyv9wNF4E3pnWnzimU312vofYnEw78R5jA7 X-Received: by 2002:a63:1750:: with SMTP id 16-v6mr9731555pgx.31.1536078339974; Tue, 04 Sep 2018 09:25:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536078339; cv=none; d=google.com; s=arc-20160816; b=QINr4i1W54SzYPhPO+4hr9PeU6XxL1E4dkIJy22g7BL/okbu08D/Vhh+w3B5E/XwD9 byD1V+ImxcemUrjJ+xU71yvT4syjCl5BB3ASKwh70mdLLUkyVYHeTQb8bpY2KldaVFrJ aY7q8jL8oCdFwr7rv0FURouolAqngQz+UedQGeL4/5OuETX+HtDCT2jH2R+oA1awNFpm Ud2QFDM3WFR9jp6Cf7C0SfJcrolssK3m6hKrJpYiivLsQU53fFCuR6TPp09b+kBstCQi OoFfOYsotJC/RYMmweFM+iTiHg9MtaSAsvvFGLbliRRnJa7k1m4+sYKQUryviKpL1l9N SeMg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=enzoTbnYeEPQjmQoHoyJ+PFkfGW0kZcrV98rSfUjhAM=; b=IySNIEGOj3Ru+PgihlnjMkgGoaW6ELiTAwpsnN1lY9Krkqxu6gD58W92y2X1O1nFiV WTK9MzI5vIy8b88Y9VRR1IP9BhciLWDl/Ljtc3PAjPQHb/uM+PKZFuzn1M9tcVVfImik z6aEWjkl4ONQF/Zty22KT0slJK9TOO3yVRI3GpwccQTUiCNMJT7ZtoO8DhYD+yx48xiN 9Py01BTY/JCFq32TnoGWRIIlNJMhFQ2Kin1v+0NEftxVZnFn/jmDD5k72ShclAYz6rgm HU2bIgZcdYOlxMscR2P1Zq2X7/GuYFdWYsnJQuhMbBluMGwSqZVaERasyhq3Q1Ao40Yq ETiA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t23-v6si21947239pgk.26.2018.09.04.09.25.24; Tue, 04 Sep 2018 09:25:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727804AbeIDUtj (ORCPT + 99 others); Tue, 4 Sep 2018 16:49:39 -0400 Received: from cust-95-128-94-82.breedbanddelft.nl ([95.128.94.82]:52658 "EHLO cust-95-128-94-82.breedbanddelft.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726052AbeIDUti (ORCPT ); Tue, 4 Sep 2018 16:49:38 -0400 Received: by abra2.bitwizard.nl (Postfix, from userid 1000) id 461F013FC78; Tue, 4 Sep 2018 18:23:48 +0200 (CEST) Date: Tue, 4 Sep 2018 18:23:48 +0200 From: Rogier Wolff To: "J. Bruce Fields" Cc: Jeff Layton , =?utf-8?B?54Sm5pmT5Yas?= , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: POSIX violation by writeback error Message-ID: <20180904162348.GN17123@BitWizard.nl> References: <20180904075347.GH11854@BitWizard.nl> <82ffc434137c2ca47a8edefbe7007f5cbecd1cca.camel@redhat.com> <20180904161203.GD17478@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180904161203.GD17478@fieldses.org> Organization: BitWizard B.V. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 04, 2018 at 12:12:03PM -0400, J. Bruce Fields wrote: > > Well, I think the point was that in the above examples you'd prefer that > the read just fail--no need to keep the data. A bit marking the file > (or even the entire filesystem) unreadable would satisfy posix, I guess. > Whether that's practical, I don't know. When you would do it like that (mark the whole filesystem as "in error") things go from bad to worse even faster. The Linux kernel tries to keep the system up even in the face of errors. With that suggestion, having one application run into a writeback error would effectively crash the whole system because the filesystem may be the root filesystem and stuff like "sshd" that you need to diagnose the problem needs to be read from the disk.... Roger. -- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** ** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 ** *-- BitWizard writes Linux device drivers for any device you may have! --* The plan was simple, like my brother-in-law Phil. But unlike Phil, this plan just might work.