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;
Date:   Thu, 15 Aug 2019 13:05:34 -0700
From:   "Darrick J. Wong" <darrick.wong@oracle.com>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     "Darrick J. Wong" <djwong@kernel.org>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        linux-xfs <linux-xfs@vger.kernel.org>,
        Dave Chinner <david@fromorbit.com>,
        Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
        Eric Sandeen <sandeen@sandeen.net>,
        Christoph Hellwig <hch@lst.de>
Subject: Re: [GIT PULL] xfs: fixes for 5.3-rc5
Message-ID: <20190815200534.GF15186@magnolia>
References: <20190815171347.GD15186@magnolia>
 <CAHk-=wiHuHLK49LKQhtERXaq0OYUnug4DJZFLPq9RHEG2Cm+bQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHk-=wiHuHLK49LKQhtERXaq0OYUnug4DJZFLPq9RHEG2Cm+bQ@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Aug 15, 2019 at 12:38:33PM -0700, Linus Torvalds wrote:
> Pulled. Just a quick note:
> 
> On Thu, Aug 15, 2019 at 10:13 AM Darrick J. Wong <djwong@kernel.org> wrote:
> >
> > - Convert more directory corruption debugging asserts to actual
> >   EFSCORRUPTED returns instead of blowing up later on.
> 
> The proper error code looks like an obvious improvement, but I do
> wonder if there should be some (ratelimited) system logging too?
> 
> I've seen a lot of programs that don't report errors very clearly and
> might just silently stop running and as a sysadmin I'd think I'd
> rather have something in the system logs than users saying "my app
> crashes at startup"/
> 
> Maybe the logging ends up being there already - just done later. It
> wasn't obvious from the patch, and I didn't check the whole callchain
> (only direct callers).

Metadata update failures hitting EFSCORRUPTED will leave a fair amount
of spew in dmesg both when we find the corrupt metadata and the update
transaction is aborted (which takes the filesystem down).  Read errors
get logged if we spot an error within a block but aren't consistently
logged when we discover problems between separate metadata objects.

FWIW I've wondered off and on if the VFS syscalls should be generating
some kind of audit trail when something returns an error message to
userspace?

--D

>                   Linus