From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Howard McLauchlan <hmclauchlan@fb.com>, linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com, Omar Sandoval <osandov@osandov.com>,
Josef Bacik <jbacik@fb.com>
Subject: Re: [PATCH v2] btrfs: print error if primary super block write fails
Date: Wed, 31 Jan 2018 08:39:31 +0800 [thread overview]
Message-ID: <1861909f-521d-6dc2-5cee-bc6c681279e4@gmx.com> (raw)
In-Reply-To: <20180130223349.5808-1-hmclauchlan@fb.com>
[-- Attachment #1.1: Type: text/plain, Size: 2242 bytes --]
On 2018年01月31日 06:33, Howard McLauchlan wrote:
> Presently, failing a primary super block write but succeeding in at
> least one super block write in general will appear to users as if
> nothing important went wrong. However, upon unmounting and re-mounting,
> the file system will be in a rolled back state. This was discovered
> with a BCC program that uses bpf_override_return() to fail super block
> writes.
>
> This patch outputs an error clarifying that the primary super block
> write has failed, so users can expect potentially erroneous behaviour.
> It also forces wait_dev_supers() to return an error to its caller if
> the primary super block write fails.
>
> Signed-off-by: Howard McLauchlan <hmclauchlan@fb.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> V2: Added devid to output, removed unnecessary fs_info parameter
>
> fs/btrfs/disk-io.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 5da18ebc9222..6d98f2f21d5f 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -3298,6 +3298,7 @@ static int wait_dev_supers(struct btrfs_device *device, int max_mirrors)
> struct buffer_head *bh;
> int i;
> int errors = 0;
> + bool primary_failed = false;
> u64 bytenr;
>
> if (max_mirrors == 0)
> @@ -3314,11 +3315,14 @@ static int wait_dev_supers(struct btrfs_device *device, int max_mirrors)
> BTRFS_SUPER_INFO_SIZE);
> if (!bh) {
> errors++;
> + primary_failed = (i == 0) || primary_failed;
> continue;
> }
> wait_on_buffer(bh);
> - if (!buffer_uptodate(bh))
> + if (!buffer_uptodate(bh)) {
> errors++;
> + primary_failed = (i == 0) || primary_failed;
> + }
>
> /* drop our reference */
> brelse(bh);
> @@ -3327,6 +3331,13 @@ static int wait_dev_supers(struct btrfs_device *device, int max_mirrors)
> brelse(bh);
> }
>
> + /* log error, force error return */
> + if (primary_failed) {
> + btrfs_err(device->fs_info, "error writing primary super block to device %llu",
> + device->devid);
> + return -1;
> + }
> +
> return errors < i ? 0 : -1;
> }
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
prev parent reply other threads:[~2018-01-31 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 22:33 [PATCH v2] btrfs: print error if primary super block write fails Howard McLauchlan
2018-01-31 0:39 ` Qu Wenruo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1861909f-521d-6dc2-5cee-bc6c681279e4@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=hmclauchlan@fb.com \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).