From: kbuild test robot <fengguang.wu@intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: kbuild-all@01.org,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
stable@kernel.org
Subject: [PATCH] ext4: fix odd_ptr_err.cocci warnings
Date: Tue, 20 Nov 2018 21:36:40 +0800 [thread overview]
Message-ID: <20181120133640.GA59775@lkp-sb-ep06> (raw)
In-Reply-To: <20181117233523.8832-1-tytso@mit.edu>
From: kbuild test robot <fengguang.wu@intel.com>
fs/ext4/resize.c:999:6-12: inconsistent IS_ERR and PTR_ERR on line 1000.
PTR_ERR should access the value just tested by IS_ERR
Semantic patch information:
There can be false positives in the patch case, where it is the call to
IS_ERR that is wrong.
Generated by: scripts/coccinelle/tests/odd_ptr_err.cocci
Fixes: 0212baa67119 ("ext4: add ext4_sb_bread() to disambiguate ENOMEM cases")
CC: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
url: https://github.com/0day-ci/linux/commits/Theodore-Ts-o/ext4-add-ext4_sb_bread-to-disambiguate-ENOMEM-cases/20181120-070629
base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
Please take the patch only if it's a positive warning. Thanks!
resize.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/fs/ext4/resize.c
+++ b/fs/ext4/resize.c
@@ -997,7 +997,7 @@ static int reserve_backup_gdb(handle_t *
}
primary[res] = ext4_sb_bread(sb, blk);
if (IS_ERR(primary[res])) {
- err = PTR_ERR(res);
+ err = PTR_ERR(primary[res]);
primary[res] = NULL;
goto exit_bh;
}
next prev parent reply other threads:[~2018-11-21 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 23:35 [PATCH] ext4: add ext4_sb_bread() to disambiguate ENOMEM cases Theodore Ts'o
2018-11-20 1:14 ` kbuild test robot
2018-11-20 13:36 ` kbuild test robot
2018-11-20 13:36 ` kbuild test robot [this message]
2018-11-22 12:21 ` Jan Kara
2018-11-22 21:12 ` Theodore Y. Ts'o
2018-11-22 22:18 ` [PATCH -v2] " Theodore Ts'o
2018-11-23 12:15 ` [PATCH] " Jan Kara
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=20181120133640.GA59775@lkp-sb-ep06 \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tytso@mit.edu \
/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).