From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [josef-btrfs:master 9/11] fs/btrfs/delayed-inode.c:1013:1-11: second lock on line 1013
Date: Fri, 03 Aug 2012 13:16:59 +0000 [thread overview]
Message-ID: <20120803131659.GA20007@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
Hi Josef,
There are (old) coccinelle warnings in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git master
head: 233564d3f5bde271885f5b784b63cfe627bba0a5
commit: ec93ee7ac77b2e95934253823918c3c684c1a36c [9/11] Btrfs: barrier before waitqueue_active
All coccinelle warnings:
+ fs/btrfs/delayed-inode.c:1013:1-11: second lock on line 1013
--
+ fs/btrfs/volumes.c:2888:1-3: WARNING: PTR_RET can be used (patch attached)
vim +1013 fs/btrfs/delayed-inode.c
1010 int ret = 0;
1011
1012 do_again:
> 1013 mutex_lock(&node->mutex);
1014 curr = __btrfs_first_delayed_deletion_item(node);
1015 if (!curr)
1016 goto delete_fail;
...
1031 if (curr)
> 1032 goto do_again;
1033 else
1034 goto delete_fail;
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
[-- Attachment #2: ptr_ret:volumes.patch --]
[-- Type: text/x-diff, Size: 413 bytes --]
Generated by: api/ptr_ret.cocci
Use PTR_RET rather than if(IS_ERR(...)) + PTR_ERR
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -2885,10 +2885,7 @@ int btrfs_resume_balance_async(struct bt
}
tsk = kthread_run(balance_kthread, fs_info, "btrfs-balance");
- if (IS_ERR(tsk))
- return PTR_ERR(tsk);
-
- return 0;
+ return PTR_RET(tsk);
}
int btrfs_recover_balance(struct btrfs_fs_info *fs_info)
next reply other threads:[~2012-08-03 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 13:16 Fengguang Wu [this message]
2012-08-03 21:11 ` [josef-btrfs:master 9/11] fs/btrfs/delayed-inode.c:1013:1-11: second lock on line 1013 Josef Bacik
2012-08-04 7:43 ` Fengguang Wu
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=20120803131659.GA20007@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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).