From: Eric Whitney <enwlinux@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Eric Whitney <enwlinux@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: clean up ext4_remove_blocks() return
Date: Fri, 14 Jul 2017 17:01:25 -0400 [thread overview]
Message-ID: <20170714210125.GA12793@localhost.localdomain> (raw)
In-Reply-To: <20170713223351.iqt4owygisqnm6wm@thunk.org>
* Theodore Ts'o <tytso@mit.edu>:
> On Thu, Jul 13, 2017 at 11:17:03AM -0400, Eric Whitney wrote:
> > ext4_remove_blocks() never returns anything other than 0, signifying
> > success. Convert the function to void type to make this immediately
> > obvious at the call site.
> >
> > Signed-off-by: Eric Whitney <enwlinux@gmail.com>
>
> Actually, what we should do is to bubble errors up from
> ext4_remove_blocks to the callers of ext4_ext_rm_leaf(). At the
> moment it doesn't return any errors, but eventually we should be
> returning errors all the way up to ext4 truncate.
>
> The reason why it's a little tricky is it's more than just not
> deleting the call to ext4_std_error() and then returning error up to
> the caller. We need to make sure that file system is in a
> self-consistent state before we return an error up to the caller.
>
> Cheers,
>
> - Ted
>
OK, that confirms a suspicion I had. That looks more like a small project
than a quick cleanup, so I'll withdraw the patch and perhaps revisit this
in the future.
Thanks,
Eric
prev parent reply other threads:[~2017-07-14 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 15:17 [PATCH] ext4: clean up ext4_remove_blocks() return Eric Whitney
2017-07-13 22:33 ` Theodore Ts'o
2017-07-14 21:01 ` Eric Whitney [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=20170714210125.GA12793@localhost.localdomain \
--to=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).