Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH 5/7] gfs2: Remove code handling bio_alloc failure with __GFP_WAIT
Date: Wed, 15 Apr 2009 09:58:48 +0100	[thread overview]
Message-ID: <1239785928.3377.1.camel@localhost.localdomain> (raw)
In-Reply-To: <200904151036.35481.knikanth@suse.de>

Hi,

Acked-by: Steven Whitehouse <swhiteho@redhat.com>

I could put this in my tree, but I think that Jens is going to push this
one to Linus, so I'm holding off,

Steve.

On Wed, 2009-04-15 at 10:36 +0530, Nikanth Karthikesan wrote:
> Remove code handling bio_alloc failure with __GFP_WAIT.
> GFP_NOFS implies __GFP_WAIT.
> 
> Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
> 
> ---
> 
> diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
> index 51883b3..650a730 100644
> --- a/fs/gfs2/ops_fstype.c
> +++ b/fs/gfs2/ops_fstype.c
> @@ -272,11 +272,6 @@ static int gfs2_read_super(struct gfs2_sbd *sdp, sector_t sector)
>  	lock_page(page);
>  
>  	bio = bio_alloc(GFP_NOFS, 1);
> -	if (unlikely(!bio)) {
> -		__free_page(page);
> -		return -ENOBUFS;
> -	}
> -
>  	bio->bi_sector = sector * (sb->s_blocksize >> 9);
>  	bio->bi_bdev = sb->s_bdev;
>  	bio_add_page(bio, page, PAGE_SIZE, 0);
> 



       reply	other threads:[~2009-04-15  8:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200904151036.35481.knikanth@suse.de>
2009-04-15  8:58 ` Steven Whitehouse [this message]
     [not found]   ` <20090415090136.GT5178@kernel.dk>
2009-04-15  9:05     ` [Cluster-devel] Re: [PATCH 5/7] gfs2: Remove code handling bio_alloc failure with __GFP_WAIT Steven Whitehouse

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=1239785928.3377.1.camel@localhost.localdomain \
    --to=swhiteho@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox