Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1732783imm; Tue, 10 Jul 2018 07:04:09 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdcCABcT+zUl0sM1PBLtW2HI3ZEi2jZakCJ++5rNzXljTDuEconwcmmfe4eKcBufA3iCj1F X-Received: by 2002:a62:9bc5:: with SMTP id e66-v6mr25626238pfk.84.1531231449764; Tue, 10 Jul 2018 07:04:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531231449; cv=none; d=google.com; s=arc-20160816; b=NpEzrAG1+hVBOQ70WxN1OqETRSTPu2Jz5Eskbkbbk44rAKut4aoYGrr4lvs+TZ3ud4 C10EM4tstmveTSVr7o/y6EDyAqGVNVH9UHYcB2zkNhSm40sSQzUPl5lOsCsA8SW83yeW 1Bwet27Qyp4ZquebWT9cBY/qgx9RRef1jZWJaUugMJ6hkk9AbIBCwziqWy+wLotO/QYM b99WlQLdqOOWfYKVW1auKoeHf9E5EFcj8Qt58yYUz3sMxIuQPzRFAdV/Lyg+7yBurZpW tTK9gG2ShgudiOUVK9zaPgf9SYbLQ3Qx95PW4ZQCO0Sx/gGXgaQax/DpEcm1nvkswTdA iofQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :dkim-signature:arc-authentication-results; bh=vE6+Iw3GvMpMXO2+RNFd+x79eZhMqTybSAbFt5Q7rNo=; b=AD7kONgR4gfhUx2MbzBz2DhPbe+TMKCCpr1RiSS2u2+c98LQtfbLWU1SKPg/g6FOEY uDX5K0NikjzIK7Y2gCo9iuscoepwvek7lt1fT6Is7j2UW3j5EmsF7sm+L0k/3YemyXgT 0fTHDiO/R1QG6erEaHndjwIHBBLqskgIHPu8/3/3kvAkLBaCJS/wRctbSbIWQRET8K9s UhKUjnEbJf8I+nhTlvcbKaWo6wPyMXeYCirIdUsMbu7oOEwxOUYV6ovszq0jMhk3gnHi B83n/20GsIB3oOd/IYjBQTfdAvGnWOj/HzGJAkHN2HfUQRUknBN1CANmrW+EJMJzP2cq LtPg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=SGc3i8Jv; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a95-v6si17123974pla.401.2018.07.10.07.03.53; Tue, 10 Jul 2018 07:04:09 -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; dkim=pass header.i=@kernel.org header.s=default header.b=SGc3i8Jv; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933468AbeGJOBc (ORCPT + 99 others); Tue, 10 Jul 2018 10:01:32 -0400 Received: from mail.kernel.org ([198.145.29.99]:34074 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933248AbeGJOBa (ORCPT ); Tue, 10 Jul 2018 10:01:30 -0400 Received: from tleilax.poochiereds.net (cpe-71-70-156-158.nc.res.rr.com [71.70.156.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4FCBC2089B; Tue, 10 Jul 2018 14:01:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1531231290; bh=r0QAqStp1Yng6IgG+avYs16dpR6ywluhcNY+b6IgL5g=; h=From:To:Cc:Subject:Date:From; b=SGc3i8JvxL0++yCjfABC21zmesELFj/rconDws4rf3vZkS0wTImNVBMDawfkzwpSD 4phetudV2ipFzLTzcurGrmrXgeQDsulY1RGcCPjl4qYZgsYqzdHQztxq9tDTL6PR0g JpDoSdmEUXwmgmCgMHADZYDvx+QlQZKA/U38UgRs= From: Jeff Layton To: viro@ZenIV.linux.org.uk, dhowells@redhat.com Cc: willy@infradead.org, andres@anarazel.de, cmaiolino@redhat.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: [PATCH v2 0/4] vfs: track per-sb writeback errors and report them via fsinfo() Date: Tue, 10 Jul 2018 10:01:23 -0400 Message-Id: <20180710140127.20739-1-jlayton@kernel.org> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org v2: drop buffer.c patch to record wb errors when underlying blockdev flush fails. We may eventually want that, but at this point I don't have a clear way to test it to determine its efficacy. At LSF/MM this year, the PostgreSQL developers mentioned that they'd like to have some mechanism to check whether there have been any writeback errors on a filesystem, without necessarily flushing any of the cached data first. Given that we have a new fsinfo syscall being introduced, we may as well use it to report writeback errors on a per superblock basis. This allows us to provide the info that the PostgreSQL developers wanted, without needing to change an existing interface. This seems to do the right thing when tested by hand, but I don't yet have an xfstest for it, since the syscall is still quite new. Once that goes in and we get fsinfo support in xfs_io, it should be rather trivial to roll a testcase for this. Al, if this looks ok, could you pull this into the branch where you have David's fsinfo patches queued up? Thanks, Jeff Jeff Layton (4): vfs: track per-sb writeback errors errseq: add a new errseq_scrape function vfs: allow fsinfo to fetch the current state of s_wb_err samples: extend test-fsinfo to access error_state fs/statfs.c | 9 +++++++++ include/linux/errseq.h | 1 + include/linux/fs.h | 3 +++ include/linux/pagemap.h | 5 ++++- include/uapi/linux/fsinfo.h | 11 +++++++++++ lib/errseq.c | 33 +++++++++++++++++++++++++++++++-- samples/statx/test-fsinfo.c | 13 +++++++++++++ 7 files changed, 72 insertions(+), 3 deletions(-) -- 2.17.1