From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cust-95-128-94-82.breedbanddelft.nl ([95.128.94.82]:43930 "EHLO cust-95-128-94-82.breedbanddelft.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727201AbeIDNxz (ORCPT ); Tue, 4 Sep 2018 09:53:55 -0400 Date: Tue, 4 Sep 2018 11:29:38 +0200 From: Rogier Wolff To: =?utf-8?B?54Sm5pmT5Yas?= Cc: jlayton@redhat.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: POSIX violation by writeback error Message-ID: <20180904092938.GJ11854@BitWizard.nl> References: <20180904075347.GH11854@BitWizard.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, Sep 04, 2018 at 04:58:59PM +0800, 焦晓冬 wrote: > As for suggestion, maybe the error flag of inode/mapping, or the entire inode > should not be evicted if there was an error. That hopefully won't take much > memory. On extreme conditions, where too much error inode requires staying > in memory, maybe we should panic rather then spread the error. Again you are hoping it will fit in memory. In an extreme case it won't fit in memory. Tyring to come up with heuristics about when to remember and when to forget such things from the past is very difficult. Think of my comments as: "it's harder than you think", not as "can't be done". 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.