All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xue jiufei <xuejiufei@huawei.com>
To: <linux-ext4@vger.kernel.org>,
	"ocfs2-devel@oss.oracle.com" <ocfs2-devel@oss.oracle.com>
Subject: A question about function jbd2__journal_restart()
Date: Tue, 14 Apr 2015 11:00:09 +0800	[thread overview]
Message-ID: <552C82B9.7060305@huawei.com> (raw)

Hi all,
I have a question about function jbd2__journal_restart().
If we call this function when there's not more credits,
it may commit the handle's transaction and start another one.
So a handle can be attached to 2 transaction and can not ensure the
consistency. It is the caller's responsibility to keep things consistently
before call jbd2__journal_restart(), right?

Thanks very much.



WARNING: multiple messages have this Message-ID (diff)
From: Xue jiufei <xuejiufei@huawei.com>
To: linux-ext4@vger.kernel.org,
	"ocfs2-devel@oss.oracle.com" <ocfs2-devel@oss.oracle.com>
Subject: [Ocfs2-devel] A question about function jbd2__journal_restart()
Date: Tue, 14 Apr 2015 11:00:09 +0800	[thread overview]
Message-ID: <552C82B9.7060305@huawei.com> (raw)

Hi all,
I have a question about function jbd2__journal_restart().
If we call this function when there's not more credits,
it may commit the handle's transaction and start another one.
So a handle can be attached to 2 transaction and can not ensure the
consistency. It is the caller's responsibility to keep things consistently
before call jbd2__journal_restart(), right?

Thanks very much.

             reply	other threads:[~2015-04-14  3:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14  3:00 Xue jiufei [this message]
2015-04-14  3:00 ` [Ocfs2-devel] A question about function jbd2__journal_restart() Xue jiufei
2015-04-14  8:43 ` Jan Kara
2015-04-14  8:43   ` [Ocfs2-devel] " Jan Kara

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=552C82B9.7060305@huawei.com \
    --to=xuejiufei@huawei.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.com \
    /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.