From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eric Whitney <enwlinux@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/4] ext4: clean up ext4_ext_handle_unwritten_extents()
Date: Thu, 21 May 2020 10:59:48 -0400 [thread overview]
Message-ID: <20200521145948.GD2939819@mit.edu> (raw)
In-Reply-To: <20200430185320.23001-1-enwlinux@gmail.com>
On Thu, Apr 30, 2020 at 02:53:16PM -0400, Eric Whitney wrote:
> Changes made to ext4 over time have resulted in some cruft accumulating
> in ext4_ext_handle_unwritten_extents(). This patch series removes
> some dead and some redundant code, simplifies and corrects some error
> handling, and adds explicit error logging when an unexpected internal
> error or file system corruption may have occurred.
>
> Eric Whitney (4):
> ext4: remove dead GET_BLOCKS_ZERO code
> ext4: remove redundant GET_BLOCKS_CONVERT code
> ext4: clean up GET_BLOCKS_PRE_IO error handling
> ext4: clean up ext4_ext_convert_to_initialized() error handling
>
> fs/ext4/extents.c | 81 ++++++++++++++++++++++++++---------------------
> 1 file changed, 45 insertions(+), 36 deletions(-)
Thanks, I've applied this patch series.
- Ted
prev parent reply other threads:[~2020-05-21 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 18:53 [PATCH 0/4] ext4: clean up ext4_ext_handle_unwritten_extents() Eric Whitney
2020-04-30 18:53 ` [PATCH 1/4] ext4: remove dead GET_BLOCKS_ZERO code Eric Whitney
2020-04-30 21:02 ` Ritesh Harjani
2020-04-30 18:53 ` [PATCH 2/4] ext4: remove redundant GET_BLOCKS_CONVERT code Eric Whitney
2020-04-30 18:53 ` [PATCH 3/4] ext4: clean up GET_BLOCKS_PRE_IO error handling Eric Whitney
2020-04-30 18:53 ` [PATCH 4/4] ext4: clean up ext4_ext_convert_to_initialized() " Eric Whitney
2020-05-21 14:59 ` Theodore Y. Ts'o [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=20200521145948.GD2939819@mit.edu \
--to=tytso@mit.edu \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@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.