cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
* [Cluster-devel] [GFS2 PATCH] GFS2: Prevent double brelse in gfs2_meta_indirect_buffer
       [not found] <1900718550.28426594.1499100383570.JavaMail.zimbra@redhat.com>
@ 2017-07-03 16:46 ` Bob Peterson
  2017-07-04  9:37   ` Steven Whitehouse
  0 siblings, 1 reply; 2+ messages in thread
From: Bob Peterson @ 2017-07-03 16:46 UTC (permalink / raw)
  To: cluster-devel.redhat.com

Hi,

Before this patch, problems reading in indirect buffers would send
an IO error back to the caller, and release the buffer_head with
brelse() in function gfs2_meta_indirect_buffer, however, it would
still return the address of the buffer_head it released. After the
error was discovered, function gfs2_block_map would call function
release_metapath to free all buffers. That checked:
if (mp->mp_bh[i] == NULL) but since the value was set after the
error, it was non-zero, so brelse was called a second time. This
resulted in the following error:

kernel: WARNING: at fs/buffer.c:1224 __brelse+0x3a/0x40()
kernel: VFS: brelse: Trying to free free buffer

This patch changes gfs2_meta_indirect_buffer so it only sets
the buffer_head pointer in cases where it isn't released.

Signed-off-by: Bob Peterson <rpeterso@redhat.com>
---
diff --git a/fs/gfs2/meta_io.c b/fs/gfs2/meta_io.c
index 663ffc1..c7d2c76 100644
--- a/fs/gfs2/meta_io.c
+++ b/fs/gfs2/meta_io.c
@@ -419,8 +419,9 @@ int gfs2_meta_indirect_buffer(struct gfs2_inode *ip, int height, u64 num,
 	if (ret == 0 && gfs2_metatype_check(sdp, bh, mtype)) {
 		brelse(bh);
 		ret = -EIO;
+	} else {
+		*bhp = bh;
 	}
-	*bhp = bh;
 	return ret;
 }
 



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

* [Cluster-devel] [GFS2 PATCH] GFS2: Prevent double brelse in gfs2_meta_indirect_buffer
  2017-07-03 16:46 ` [Cluster-devel] [GFS2 PATCH] GFS2: Prevent double brelse in gfs2_meta_indirect_buffer Bob Peterson
@ 2017-07-04  9:37   ` Steven Whitehouse
  0 siblings, 0 replies; 2+ messages in thread
From: Steven Whitehouse @ 2017-07-04  9:37 UTC (permalink / raw)
  To: cluster-devel.redhat.com

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

Steve.


On 03/07/17 17:46, Bob Peterson wrote:
> Hi,
>
> Before this patch, problems reading in indirect buffers would send
> an IO error back to the caller, and release the buffer_head with
> brelse() in function gfs2_meta_indirect_buffer, however, it would
> still return the address of the buffer_head it released. After the
> error was discovered, function gfs2_block_map would call function
> release_metapath to free all buffers. That checked:
> if (mp->mp_bh[i] == NULL) but since the value was set after the
> error, it was non-zero, so brelse was called a second time. This
> resulted in the following error:
>
> kernel: WARNING: at fs/buffer.c:1224 __brelse+0x3a/0x40()
> kernel: VFS: brelse: Trying to free free buffer
>
> This patch changes gfs2_meta_indirect_buffer so it only sets
> the buffer_head pointer in cases where it isn't released.
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> ---
> diff --git a/fs/gfs2/meta_io.c b/fs/gfs2/meta_io.c
> index 663ffc1..c7d2c76 100644
> --- a/fs/gfs2/meta_io.c
> +++ b/fs/gfs2/meta_io.c
> @@ -419,8 +419,9 @@ int gfs2_meta_indirect_buffer(struct gfs2_inode *ip, int height, u64 num,
>   	if (ret == 0 && gfs2_metatype_check(sdp, bh, mtype)) {
>   		brelse(bh);
>   		ret = -EIO;
> +	} else {
> +		*bhp = bh;
>   	}
> -	*bhp = bh;
>   	return ret;
>   }
>   
>



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

end of thread, other threads:[~2017-07-04  9:37 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <1900718550.28426594.1499100383570.JavaMail.zimbra@redhat.com>
2017-07-03 16:46 ` [Cluster-devel] [GFS2 PATCH] GFS2: Prevent double brelse in gfs2_meta_indirect_buffer Bob Peterson
2017-07-04  9:37   ` Steven Whitehouse

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