From: Theodore Tso <tytso@mit.edu>
To: Akira Fujita <a-fujita@rs.jp.nec.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/4]ext4: Replace BUG_ON() with ext4_error() in move_extents.c
Date: Wed, 16 Sep 2009 14:18:05 -0400 [thread overview]
Message-ID: <20090916181805.GD15451@mit.edu> (raw)
In-Reply-To: <4AADFC0F.9010205@rs.jp.nec.com>
On Mon, Sep 14, 2009 at 05:17:19PM +0900, Akira Fujita wrote:
> ext4: Replace BUG_ON() with ext4_error() in move_extents.c
>
> From: Akira Fujita <a-fujita@rs.jp.nec.com>
>
> Replace BUG_ON calls with a call to ext4_error()
> to print an error message if EXT4_IOC_MOVE_EXT failed
> with some kind of reasons. This will help to debug.
> Ted pointed this out, thanks.
>
> Signed-off-by: Akira Fujita <a-fujita@rs.jp.nec.com>
Applied, thanks.
- Ted
prev parent reply other threads:[~2009-09-16 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 8:17 [PATCH 2/4]ext4: Replace BUG_ON() with ext4_error() in move_extents.c Akira Fujita
2009-09-16 18:18 ` Theodore Tso [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=20090916181805.GD15451@mit.edu \
--to=tytso@mit.edu \
--cc=a-fujita@rs.jp.nec.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 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).