From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 Patch] Fix recent use-after-free spotted by coverity
Date: Mon, 09 Jan 2012 15:40:38 +0000 [thread overview]
Message-ID: <1326123638.2690.39.camel@menhir> (raw)
In-Reply-To: <8d419c53-d6cc-4cdf-b8ce-318809dc1fae@zmail16.collab.prod.int.phx2.redhat.com>
Hi,
Now in the -fixes tree. Thanks,
Steve.
On Fri, 2012-01-06 at 16:48 -0500, Bob Peterson wrote:
> Hi,
>
> This patch fixes a use-after-free bug, spotted by coverity, which
> was recently introduced.
>
> Regards,
>
> Bob Peterson
> Red Hat File Systems
>
> Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> --
> Author: Bob Peterson <rpeterso@redhat.com>
> Date: Fri Jan 6 16:42:27 2012 -0600
>
> GFS2: Fix a use-after-free that coverity spotted
>
> In function gfs2_inplace_release it was trying to unlock a gfs2_holder
> structure associated with a reservation, after said reservation was
> freed. The problem is that the statements have the wrong order.
> This patch corrects the order so that the reservation is freed after
> the gfs2_holder is unlocked.
>
> diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
> index 2223462..981bfa3 100644
> --- a/fs/gfs2/rgrp.c
> +++ b/fs/gfs2/rgrp.c
> @@ -1108,9 +1108,9 @@ void gfs2_inplace_release(struct gfs2_inode *ip)
> {
> struct gfs2_blkreserv *rs = ip->i_res;
>
> - gfs2_blkrsv_put(ip);
> if (rs->rs_rgd_gh.gh_gl)
> gfs2_glock_dq_uninit(&rs->rs_rgd_gh);
> + gfs2_blkrsv_put(ip);
> }
>
> /**
>
prev parent reply other threads:[~2012-01-09 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8a91332c-d06e-4a6a-9672-dcd2ebe261f6@zmail16.collab.prod.int.phx2.redhat.com>
2012-01-06 21:48 ` [Cluster-devel] [GFS2 Patch] Fix recent use-after-free spotted by coverity Bob Peterson
2012-01-09 15:40 ` Steven Whitehouse [this message]
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=1326123638.2690.39.camel@menhir \
--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;
as well as URLs for NNTP newsgroup(s).