diff options
author | Howard McLauchlan <hmclauchlan@fb.com> | 2018-02-02 20:09:01 +0100 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2018-03-26 15:09:29 +0200 |
commit | b6a535faed06c2bdfaf55b00025dfdcb1eadf980 (patch) | |
tree | dab689f8d38fb490352bd0dbe60a4cd5c94f58b2 /fs/btrfs/transaction.h | |
parent | btrfs: Refactor parameter of BTRFS_MAX_DEVS() from root to fs_info (diff) | |
download | linux-b6a535faed06c2bdfaf55b00025dfdcb1eadf980.tar.xz linux-b6a535faed06c2bdfaf55b00025dfdcb1eadf980.zip |
btrfs: print error if primary super block write fails
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>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/transaction.h')
0 files changed, 0 insertions, 0 deletions