All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Manish Katiyar <mkatiyar@gmail.com>
Cc: Ted Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH 2/3] jbd2 : Fix journal start by passing a parameter to specify if the caller can deal with ENOMEM
Date: Thu, 26 May 2011 16:51:51 +0200	[thread overview]
Message-ID: <20110526145151.GC5123@quack.suse.cz> (raw)
In-Reply-To: <BANLkTi=QuZfvDohsawA75kWQuYuJvsHQiA@mail.gmail.com>

  Hi Manish,

On Wed 25-05-11 22:29:59, Manish Katiyar wrote:
> On Wed, May 25, 2011 at 7:22 PM, Ted Ts'o <tytso@mit.edu> wrote:
> > On Wed, May 25, 2011 at 10:13:33AM +0200, Jan Kara wrote:
> >> >
> >> >    ok.. I will do it as a separate patch.
> >>   Well, patch 2/3 does not really make too much sense without it (errok
> >> parameter isn't used) so there's no reason to do it as a separate patch.
> >> Just add it to this patch please.
> >
> > Agreed; right now this whole patch series is a no-op, since errok
> > isn't getting used for anything.  So fixing errok so it's passed to
> > start_this_handle() seems to be more in the category of "fix the
> > patch" more than anything else.
> >
> > One more thing; perhaps we should be passing in a integer so we can
> > pass in a flag word.  That way you don't need to have a fail_ok
> > variant.  It's a lot more obvious if you have a call:
> >
> >          handle = ext4_journal_start(inode, 1, JBD2_FAIL_OK);
> >
> > What we can also do is this:
> >
> >          handle = ext4_journal_start(inode, 1, JBD2_FAIL_OK | JBD2_TOPLEVEL);
> >
> > What JBD2_TOPLEVEL means is that caller is from a top-level file
> > system function, such as ext4_symlink() or ext4_chmod(), such that
> > start_this_handle() can use GFP_KERNEL instead of GFP_NOFS.  GFP_NOFS
> > is needed for any function that might get called by the direct reclaim
> > path (i.e., the writepage() function).  But for the top-level
> > symlink() or chmod() function, it's actually OK to allocate memory
> > using GFP_KERNEL, since there's no potential recursion problem.
> 
> Will it be more desirable to have the patch fixed as JBD2_FAIL_OK as
> you suggested above ? I have already
> fixed the patch to pass errok to start_this_handle() and then retry or
> not based on that, and was planning to send
> it. But if this needs to be fixed this way, then I will rework it then send.
  Well, I don't care much and Ted seems to like flags more. As he is the
maintainer, I guess just follow his advice ;).

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-05-26 14:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  7:26 [PATCH 2/3] jbd2 : Fix journal start by passing a parameter to specify if the caller can deal with ENOMEM Manish Katiyar
2011-05-25  7:44 ` Jan Kara
2011-05-25  7:47   ` Manish Katiyar
2011-05-25  8:13     ` Jan Kara
2011-05-26  2:22       ` Ted Ts'o
2011-05-26  4:07         ` Andreas Dilger
2011-05-26 14:05           ` Ted Ts'o
2011-05-26 14:49             ` Jan Kara
2011-05-26 15:08               ` Ted Ts'o
2011-05-26 15:37                 ` Jan Kara
2011-05-27  4:11                 ` Manish Katiyar
2011-05-26  5:29         ` Manish Katiyar
2011-05-26 14:51           ` Jan Kara [this message]
2011-05-28  6:16         ` Manish Katiyar

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=20110526145151.GC5123@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mkatiyar@gmail.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 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.