public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Tahsin Erdogan <tahsin@google.com>, Theodore Ts'o <tytso@mit.edu>,
	Jan Kara <jack@suse.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jbd2: preserve original nofs flag during journal restart
Date: Wed, 17 May 2017 17:24:32 +0200	[thread overview]
Message-ID: <20170517152432.GA20660@dhcp22.suse.cz> (raw)
In-Reply-To: <20170517145627.GB5632@quack2.suse.cz>

On Wed 17-05-17 16:56:27, Jan Kara wrote:
> On Wed 17-05-17 16:13:57, Michal Hocko wrote:
> > On Wed 17-05-17 05:33:01, Tahsin Erdogan wrote:
> > > When a transaction starts, start_this_handle() saves current
> > > PF_MEMALLOC_NOFS value so that it can be restored at journal stop time.
> > > Journal restart is a special case that calls start_this_handle() without
> > > stopping the transaction. start_this_handle() isn't aware that the
> > > original value is already stored so it overwrites it with current value.
> > > 
> > > For instance, a call sequence like below leaves PF_MEMALLOC_NOFS flag set
> > > at the end:
> > > 
> > >   jbd2_journal_start()
> > >   jbd2__journal_restart()
> > >   jbd2_journal_stop()
> > > 
> > > Make jbd2__journal_restart() restore the original value before calling
> > > start_this_handle().
> > > 
> > > Fixes: 81378da64de6 ("jbd2: mark the transaction context with the scope GFP_NOFS context")
> > > Signed-off-by: Tahsin Erdogan <tahsin@google.com>
> > > ---
> > >  fs/jbd2/transaction.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/fs/jbd2/transaction.c b/fs/jbd2/transaction.c
> > > index 9ee4832b6f8b..dfd6afebdfeb 100644
> > > --- a/fs/jbd2/transaction.c
> > > +++ b/fs/jbd2/transaction.c
> > > @@ -680,6 +680,7 @@ int jbd2__journal_restart(handle_t *handle, int nblocks, gfp_t gfp_mask)
> > >  
> > >  	rwsem_release(&journal->j_trans_commit_map, 1, _THIS_IP_);
> > >  	handle->h_buffer_credits = nblocks;
> > > +	memalloc_nofs_restore(handle->saved_alloc_context);
> > >  	ret = start_this_handle(journal, handle, gfp_mask);
> > >  	return ret;
> > >  }
> > 
> > I remember Jack has mentioned something about nested transaction back
> > then when reviewing the patch. But I cannot remember or find a pointer
> > to that email. I have a vague recollection that there is a reference
> > counting for those transactions.
> > 
> > Anyway, Is this patch really correct? So let's say we are in
> > the transaction context already and then you disable the scope
> > NOFS protection, start_this_handle will allocate before it calls
> > memalloc_nofs_save and that would recurse to the filesystem.  If
> > anything wouldn't it be better to simply call memalloc_nofs_save only if
> > we start a new transaction? I thought we were doing that already but the
> > code is so convoluted I have hard time to wrap my head around it.
> 
> I was thinking about his as well but the fact is jbd2__journal_restart()
> actually does equivalent of jbd2_journal_stop() for the handle above the
> place where memalloc_nofs_restore() was added so in this sense we really
> miss memalloc_nofs_restore() there... So what Tahsin did makes sense.

OK, I will trust you ;). This deserves a comment then, I believe.

Thanks!
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2017-05-17 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 12:33 [PATCH] jbd2: preserve original nofs flag during journal restart Tahsin Erdogan
2017-05-17 14:04 ` Jan Kara
2017-05-17 14:13 ` Michal Hocko
2017-05-17 14:56   ` Jan Kara
2017-05-17 15:24     ` Michal Hocko [this message]
2017-05-17 16:16       ` [PATCH v2] " Tahsin Erdogan
2017-05-18  9:12         ` Michal Hocko
2017-05-18  9:39           ` Jan Kara
2017-05-18 16:28             ` [PATCH v3] " Tahsin Erdogan
2017-05-20  4:09               ` Theodore Ts'o

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=20170517152432.GA20660@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tahsin@google.com \
    --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