linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH] Btrfs: deal with unexpected return value in flush_space
Date: Thu, 28 Jul 2016 11:49:14 -0700	[thread overview]
Message-ID: <20160728184914.GA29799@localhost.localdomain> (raw)
In-Reply-To: <pan$5450c$1d8fe409$834c6bbc$1311860c@applied-asynchrony.com>

On Thu, Jul 28, 2016 at 03:36:53PM +0000, Holger Hoffstätte wrote:
> On Wed, 27 Jul 2016 18:42:03 -0700, Liu Bo wrote:
> 
> > Function start_transaction() can return ERR_PTR(1) when flush is
> > BTRFS_RESERVE_FLUSH_LIMIT, so the call graph is
> > 
> > start_transaction (return ERR_PTR(1))
> >   -> btrfs_block_rsv_add (return 1)
> >      -> reserve_metadata_bytes (return 1)
> >         -> flush_space (return 1)
> >            -> do_chunk_alloc  (return 1)
> > 
> > With BTRFS_RESERVE_FLUSH_LIMIT, if flush_space is already on the
> > flush_state of ALLOC_CHUNK and it successfully allocates a new
> > chunk, then instead of trying to reserve space again,
> > reserve_metadata_bytes returns 1 immediately.
> > 
> > Eventually the callers who call start_transaction() usually just
> > do the IS_ERR() check which ERR_PTR(1) can pass, then it'll get
> > a panic when dereferencing a pointer which is ERR_PTR(1).
> > 
> > This makes flush_space() translate 'ret = 1' to 'ret = 0'.
> > 
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> > We found this 'NULL pointer dereference' on an old 3.8 kernel but
> > it's not going to happen on the upstream since there is no caller
> > of btrfs_start_transaction_lflush().
> > 
> >  fs/btrfs/extent-tree.c | 11 ++++++++++-
> >  1 file changed, 10 insertions(+), 1 deletion(-)
> > 
> > diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> > index 7a35c9d..a00fb67 100644
> > --- a/fs/btrfs/extent-tree.c
> > +++ b/fs/btrfs/extent-tree.c
> > @@ -4457,6 +4457,15 @@ void check_system_chunk(struct btrfs_trans_handle *trans,
> >  	}
> >  }
> >  
> > +/*
> > + * If force is CHUNK_ALLOC_FORCE:
> > + *    - return 1 if it successfully allocates a chunk,
> > + *    - return errors including -ENOSPC otherwise.
> > + * If force is NOT CHUNK_ALLOC_FORCE:
> > + *    - return 0 if it doesn't need to allocate a new chunk,
> > + *    - return 1 if it successfully allocates a chunk,
> > + *    - return errors including -ENOSPC otherwise.
> > + */
> >  static int do_chunk_alloc(struct btrfs_trans_handle *trans,
> >  			  struct btrfs_root *extent_root, u64 flags, int force)
> >  {
> > @@ -4857,7 +4866,7 @@ static int flush_space(struct btrfs_root *root,
> >  				     btrfs_get_alloc_profile(root, 0),
> >  				     CHUNK_ALLOC_NO_FORCE);
> >  		btrfs_end_transaction(trans, root);
> > -		if (ret == -ENOSPC)
> > +		if (ret == -ENOSPC || ret == 1)
> >  			ret = 0;
> >  		break;
> >  	case COMMIT_TRANS:
> > -- 
> > 2.5.5
> 
> For reviewers - this came up before here:
> https://patchwork.kernel.org/patch/7778651/
> 
> Same fix basically.

Aha, I've given it my Reviewed-by.

Taking either one works for me, I can make the clarifying comment into a
seperate patch if we need to.

Thanks,

-liubo

  reply	other threads:[~2016-07-28 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28  1:42 [PATCH] Btrfs: deal with unexpected return value in flush_space Liu Bo
2016-07-28 15:36 ` Holger Hoffstätte
2016-07-28 18:49   ` Liu Bo [this message]
2016-07-29 17:01     ` David Sterba
2016-07-29 17:53       ` Liu Bo
2016-10-01 20:13         ` Alex Lyakas
2016-07-29 18:09 ` [PATCH v2] Btrfs: clarify do_chunk_alloc()'s return value Liu Bo
2016-08-18 12:36   ` David Sterba

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=20160728184914.GA29799@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=holger@applied-asynchrony.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 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).