From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=-10.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT 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 EE338C35242 for ; Fri, 7 Feb 2020 17:04:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BB6A821927 for ; Fri, 7 Feb 2020 17:04:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1581095078; bh=ZxvKRMhl7lIThcnne9emlNMv0Ks2BQRDLcIh5ixelek=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=mbw7sQgC0/FCZmX0GrYT+dupBCbeNm68QrIv0XtQt8Uh1+1HP2nTd+TQpDgGKcg0S T8NfW2H7dLCLlb9pjr1vp/Lzz8QgD3EY6rmyRvYrouzYnxua0XSUsgMjcEJN8OEKWs D/HUKyl/rE6cL7TYrt4ZnMfUpPnYO55Z61AziKpI= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726951AbgBGREi (ORCPT ); Fri, 7 Feb 2020 12:04:38 -0500 Received: from mail.kernel.org ([198.145.29.99]:52942 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727309AbgBGRE2 (ORCPT ); Fri, 7 Feb 2020 12:04:28 -0500 Received: from tleilax.poochiereds.net (68-20-15-154.lightspeed.rlghnc.sbcglobal.net [68.20.15.154]) (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 5837721775; Fri, 7 Feb 2020 17:04:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1581095068; bh=ZxvKRMhl7lIThcnne9emlNMv0Ks2BQRDLcIh5ixelek=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ixqV4Vj9ZtMDKL2uwwsmYIuCMMTiJgzkyW3Q5SIfbS/E5WdnX4Hl2Ug5YTxXQwf4M syoAt6TqtpBQGciunxTzImNBlzlGoqs2yuBF2+HQ/Wrrox2J3uZ9JyrGIQr5hzhh3v P2Mb9CuDd3I/2h/didpKn+nf0d+XHtK5eJv2ECkE= From: Jeff Layton To: viro@zeniv.linux.org.uk Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, andres@anarazel.de, willy@infradead.org, dhowells@redhat.com, hch@infradead.org, jack@suse.cz, akpm@linux-foundation.org Subject: [PATCH v3 2/3] buffer: record blockdev write errors in super_block that it backs Date: Fri, 7 Feb 2020 12:04:22 -0500 Message-Id: <20200207170423.377931-3-jlayton@kernel.org> X-Mailer: git-send-email 2.24.1 In-Reply-To: <20200207170423.377931-1-jlayton@kernel.org> References: <20200207170423.377931-1-jlayton@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org From: Jeff Layton When syncing out a block device (a'la __sync_blockdev), any error encountered will only be recorded in the bd_inode's mapping. When the blockdev contains a filesystem however, we'd like to also record the error in the super_block that's stored there. Make mark_buffer_write_io_error also record the error in the corresponding super_block when a writeback error occurs and the block device contains a mounted superblock. Signed-off-by: Jeff Layton --- fs/buffer.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/buffer.c b/fs/buffer.c index b8d28370cfd7..451f1be6e1a4 100644 --- a/fs/buffer.c +++ b/fs/buffer.c @@ -1166,6 +1166,8 @@ void mark_buffer_write_io_error(struct buffer_head *bh) mapping_set_error(bh->b_page->mapping, -EIO); if (bh->b_assoc_map) mapping_set_error(bh->b_assoc_map, -EIO); + if (bh->b_bdev->bd_super) + errseq_set(&bh->b_bdev->bd_super->s_wb_err, -EIO); } EXPORT_SYMBOL(mark_buffer_write_io_error); -- 2.24.1