linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* A question about function jbd2__journal_restart()
@ 2015-04-14  3:00 Xue jiufei
  2015-04-14  8:43 ` Jan Kara
  0 siblings, 1 reply; 2+ messages in thread
From: Xue jiufei @ 2015-04-14  3:00 UTC (permalink / raw)
  To: linux-ext4, ocfs2-devel@oss.oracle.com

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.



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: A question about function jbd2__journal_restart()
  2015-04-14  3:00 A question about function jbd2__journal_restart() Xue jiufei
@ 2015-04-14  8:43 ` Jan Kara
  0 siblings, 0 replies; 2+ messages in thread
From: Jan Kara @ 2015-04-14  8:43 UTC (permalink / raw)
  To: Xue jiufei; +Cc: linux-ext4, ocfs2-devel@oss.oracle.com

  Hello,

On Tue 14-04-15 11:00:09, Xue jiufei wrote:
> 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?
  Correct.

								Honza

-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-04-14  8:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-14  3:00 A question about function jbd2__journal_restart() Xue jiufei
2015-04-14  8:43 ` Jan Kara

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).