From: Alex Elder <aelder@sgi.com>
To: Julia Lawall <julia@diku.dk>
Cc: xfs-masters@oss.sgi.com, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 11/17] fs/xfs/quota: Add missing mutex_unlock
Date: Fri, 28 May 2010 17:57:32 +0000 [thread overview]
Message-ID: <1275069452.2302.5.camel@doink> (raw)
In-Reply-To: <Pine.LNX.4.64.1005261757050.23743@ask.diku.dk>
On Wed, 2010-05-26 at 17:57 +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> Add a mutex_unlock missing on the error path. The use of this lock is
> balanced elsewhere in the file.
Looks good. I'll pull this one into the XFS tree.
Reviewed-by: Alex Elder <aelder@sgi.com>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression E1;
> @@
>
> * mutex_lock(E1,...);
> <+... when != E1
> if (...) {
> ... when != E1
> * return ...;
> }
> ...+>
> * mutex_unlock(E1,...);
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> The use of ENOMEM rather than -ENOMEM is also a bit odd.
>
> fs/xfs/quota/xfs_qm.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/quota/xfs_qm.c b/fs/xfs/quota/xfs_qm.c
> index 38e7641..2d8b7bc 100644
> --- a/fs/xfs/quota/xfs_qm.c
> +++ b/fs/xfs/quota/xfs_qm.c
> @@ -249,8 +249,10 @@ xfs_qm_hold_quotafs_ref(
>
> if (!xfs_Gqm) {
> xfs_Gqm = xfs_Gqm_init();
> - if (!xfs_Gqm)
> + if (!xfs_Gqm) {
> + mutex_unlock(&xfs_Gqm_lock);
> return ENOMEM;
> + }
> }
>
> /*
WARNING: multiple messages have this Message-ID (diff)
From: Alex Elder <aelder@sgi.com>
To: Julia Lawall <julia@diku.dk>
Cc: xfs-masters@oss.sgi.com, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 11/17] fs/xfs/quota: Add missing mutex_unlock
Date: Fri, 28 May 2010 12:57:32 -0500 [thread overview]
Message-ID: <1275069452.2302.5.camel@doink> (raw)
In-Reply-To: <Pine.LNX.4.64.1005261757050.23743@ask.diku.dk>
On Wed, 2010-05-26 at 17:57 +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> Add a mutex_unlock missing on the error path. The use of this lock is
> balanced elsewhere in the file.
Looks good. I'll pull this one into the XFS tree.
Reviewed-by: Alex Elder <aelder@sgi.com>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression E1;
> @@
>
> * mutex_lock(E1,...);
> <+... when != E1
> if (...) {
> ... when != E1
> * return ...;
> }
> ...+>
> * mutex_unlock(E1,...);
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> The use of ENOMEM rather than -ENOMEM is also a bit odd.
>
> fs/xfs/quota/xfs_qm.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/quota/xfs_qm.c b/fs/xfs/quota/xfs_qm.c
> index 38e7641..2d8b7bc 100644
> --- a/fs/xfs/quota/xfs_qm.c
> +++ b/fs/xfs/quota/xfs_qm.c
> @@ -249,8 +249,10 @@ xfs_qm_hold_quotafs_ref(
>
> if (!xfs_Gqm) {
> xfs_Gqm = xfs_Gqm_init();
> - if (!xfs_Gqm)
> + if (!xfs_Gqm) {
> + mutex_unlock(&xfs_Gqm_lock);
> return ENOMEM;
> + }
> }
>
> /*
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Alex Elder <aelder@sgi.com>
To: Julia Lawall <julia@diku.dk>
Cc: xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 11/17] fs/xfs/quota: Add missing mutex_unlock
Date: Fri, 28 May 2010 12:57:32 -0500 [thread overview]
Message-ID: <1275069452.2302.5.camel@doink> (raw)
In-Reply-To: <Pine.LNX.4.64.1005261757050.23743@ask.diku.dk>
On Wed, 2010-05-26 at 17:57 +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> Add a mutex_unlock missing on the error path. The use of this lock is
> balanced elsewhere in the file.
Looks good. I'll pull this one into the XFS tree.
Reviewed-by: Alex Elder <aelder@sgi.com>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression E1;
> @@
>
> * mutex_lock(E1,...);
> <+... when != E1
> if (...) {
> ... when != E1
> * return ...;
> }
> ...+>
> * mutex_unlock(E1,...);
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> The use of ENOMEM rather than -ENOMEM is also a bit odd.
>
> fs/xfs/quota/xfs_qm.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/quota/xfs_qm.c b/fs/xfs/quota/xfs_qm.c
> index 38e7641..2d8b7bc 100644
> --- a/fs/xfs/quota/xfs_qm.c
> +++ b/fs/xfs/quota/xfs_qm.c
> @@ -249,8 +249,10 @@ xfs_qm_hold_quotafs_ref(
>
> if (!xfs_Gqm) {
> xfs_Gqm = xfs_Gqm_init();
> - if (!xfs_Gqm)
> + if (!xfs_Gqm) {
> + mutex_unlock(&xfs_Gqm_lock);
> return ENOMEM;
> + }
> }
>
> /*
next prev parent reply other threads:[~2010-05-28 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 15:57 [PATCH 11/17] fs/xfs/quota: Add missing mutex_unlock Julia Lawall
2010-05-26 15:57 ` Julia Lawall
2010-05-26 15:57 ` Julia Lawall
2010-05-28 17:57 ` Alex Elder [this message]
2010-05-28 17:57 ` Alex Elder
2010-05-28 17:57 ` Alex Elder
2010-06-02 3:34 ` [xfs-masters] " Eric Sandeen
2010-06-02 3:34 ` Eric Sandeen
2010-06-02 3:34 ` Eric Sandeen
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=1275069452.2302.5.camel@doink \
--to=aelder@sgi.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.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 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.