All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Josef Bacik <josef@toxicpanda.com>,
	linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v4 0/5] Miscellaneous error handling patches
Date: Wed, 6 Oct 2021 17:22:34 +0300	[thread overview]
Message-ID: <3c335928-1eec-6a92-b657-a9ac5f4d2895@suse.com> (raw)
In-Reply-To: <cover.1633465964.git.josef@toxicpanda.com>



On 5.10.21 г. 23:35, Josef Bacik wrote:
> v3->v4:
> - Added another abort() call that I missed in btrfs_recover_log_trees.
> - Updated the commit message for 'btrfs: change error handling for
>   btrfs_delete_*_in_log' as it pre-dated me figuring out there was a corruption
>   problem in sync log.
> - Fixed commit message for 'btrfs: add a BTRFS_FS_ERROR helper'.
> - Made it so 'btrfs: do not infinite loop in data reclaim if we aborted'
>   actually compiled, I guess my compile after rebase git hook didn't quite work
>   as expected.
> - Updated the comment in 'btrfs: fix abort logic in btrfs_replace_file_extents'.
> - Rebased onto misc-next.
> 
> --- Original email ---
> Hello,
> 
> This series is left overs from a few different series.  The error handling
> patches look like they just got missed somehow.  The FS_ERROR helper has been
> updated based on the comments from Dave.  I'm attaching this to the open GH
> thing that I was looking at to update, but really just has the FS_ERROR helper
> patch from that series.  Thanks,
> 
> Josef
> 
> Josef Bacik (5):
>   btrfs: change handle_fs_error in recover_log_trees to aborts
>   btrfs: change error handling for btrfs_delete_*_in_log
>   btrfs: add a BTRFS_FS_ERROR helper
>   btrfs: do not infinite loop in data reclaim if we aborted
>   btrfs: fix abort logic in btrfs_replace_file_extents
> 
>  fs/btrfs/ctree.h       |  3 ++
>  fs/btrfs/disk-io.c     |  8 ++----
>  fs/btrfs/extent_io.c   |  2 +-
>  fs/btrfs/file.c        | 18 ++++++------
>  fs/btrfs/inode.c       | 22 ++++-----------
>  fs/btrfs/scrub.c       |  2 +-
>  fs/btrfs/space-info.c  | 27 +++++++++++++++---
>  fs/btrfs/super.c       |  2 +-
>  fs/btrfs/transaction.c | 11 ++++----
>  fs/btrfs/tree-log.c    | 62 ++++++++++++++++--------------------------
>  fs/btrfs/tree-log.h    | 16 +++++------
>  11 files changed, 85 insertions(+), 88 deletions(-)
> 


All the changes are straightforward so:

Reviewed-by: Nikolay Borisov <nborisov@suse.com>

  parent reply	other threads:[~2021-10-06 14:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 20:35 [PATCH v4 0/5] Miscellaneous error handling patches Josef Bacik
2021-10-05 20:35 ` [PATCH v4 1/5] btrfs: change handle_fs_error in recover_log_trees to aborts Josef Bacik
2021-10-05 20:35 ` [PATCH v4 2/5] btrfs: change error handling for btrfs_delete_*_in_log Josef Bacik
2021-10-06 17:17   ` Filipe Manana
2021-10-06 19:03   ` David Sterba
2021-10-05 20:35 ` [PATCH v4 3/5] btrfs: add a BTRFS_FS_ERROR helper Josef Bacik
2021-10-06 19:11   ` David Sterba
2021-10-05 20:35 ` [PATCH v4 4/5] btrfs: do not infinite loop in data reclaim if we aborted Josef Bacik
2021-10-06 17:19   ` Filipe Manana
2021-10-05 20:35 ` [PATCH v4 5/5] btrfs: fix abort logic in btrfs_replace_file_extents Josef Bacik
2021-10-06 17:16   ` Filipe Manana
2021-10-06 14:22 ` Nikolay Borisov [this message]
2021-10-06 19:23 ` [PATCH v4 0/5] Miscellaneous error handling patches David Sterba

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=3c335928-1eec-6a92-b657-a9ac5f4d2895@suse.com \
    --to=nborisov@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.