From: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org, chris.mason@oracle.com
Subject: Re: [PATCH] btrfs: fix return value check of btrfs_start_transaction()
Date: Fri, 21 Jan 2011 08:47:12 +0900 [thread overview]
Message-ID: <4D38C980.3020001@jp.fujitsu.com> (raw)
In-Reply-To: <20110120160959.GB6609@dhcp231-156.rdu.redhat.com>
(2011/01/21 1:09), Josef Bacik wrote:
> I'd rather we go through and have these things return an error than d=
o a
> BUG_ON(). We're moving towards a more stable BTRFS, not one that pan=
ics more
> often :).
Yes, I also think so.
This patch is my first step.
My modification policy is as follows:
1. short term
- To more stable BTRFS, the part that should be corrected is clarified=
=2E=20
- The panic is not done by the NULL pointer reference etc.
2. long term
=E3=80=80- BUG_ON() is decreased by using the forced-readonly framework=
(already posted by Liu Bo),
etc.=20
Thanks,
Itoh
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-20 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 6:19 [PATCH] btrfs: fix return value check of btrfs_start_transaction() Tsutomu Itoh
2011-01-20 16:09 ` Josef Bacik
2011-01-20 23:47 ` Tsutomu Itoh [this message]
2011-01-21 6:06 ` Tsutomu Itoh
2011-01-28 21:53 ` Chris Mason
2011-01-31 0:03 ` Tsutomu Itoh
2011-02-01 2:15 ` Tsutomu Itoh
2011-02-01 12:38 ` Chris Mason
2011-01-21 1:59 ` liubo
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=4D38C980.3020001@jp.fujitsu.com \
--to=t-itoh@jp.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.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.