From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Zheng Liu <wenqing.lz@taobao.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: [PATCH] debugfs: fix two warning messages when compiling with LLVM (Re: compile warning on master)
Date: Mon, 26 May 2014 14:55:08 +0800 [thread overview]
Message-ID: <20140526065508.GA4591@gmail.com> (raw)
In-Reply-To: <65EABAA6-4117-4059-B04D-0E0D77D698CE@dilger.ca>
On Tue, May 20, 2014 at 05:14:34PM -0600, Andreas Dilger wrote:
>
> When compiling with LLVM, it generates the following warning in
> debugfs::do_lsdel():
>
> 367 debugfs/lsdel.c:155 col 23: warning: '&&' within '||'
> [-Wlogical-op-parentheses]
> 368: if (lsd.free_blocks && !lsd.bad_blocks ||
> 369: ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~ ~~
> 370 debugfs/lsdel.c:155 col 23: note: place parentheses around the '&&'
> expression to silence this warning
> 371: if (lsd.free_blocks && !lsd.bad_blocks ||
> 372: ^
> 373: ( )
>
>
> Unfortunately, even looking at this code and the patch that changed it,
> I can't figure out what the correct parenthesis is for it.
>
> Zheng, could you please send a patch to fix this?
Thanks for reporting this. Could you please try the following patch?
Regards,
- Zheng
Subject: [PATCH] debugfs: fix two warning messages when compiling with LLVM
From: Zheng Liu <wenqing.lz@taobao.com>
This commit fixes two warning messages when compiling with LLVM.
Cc: "Theodore Ts'o" <tytso@mit.edu>
Cc: Andreas Dilger <adilger@dilger.ca>
Reported-by: Andreas Dilger <adilger@dilger.ca>
Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
---
debugfs/lsdel.c | 2 +-
lib/ext2fs/inline_data.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/debugfs/lsdel.c b/debugfs/lsdel.c
index 5276014..a7c30b3 100644
--- a/debugfs/lsdel.c
+++ b/debugfs/lsdel.c
@@ -152,7 +152,7 @@ void do_lsdel(int argc, char **argv)
goto next;
}
}
- if (lsd.free_blocks && !lsd.bad_blocks ||
+ if ((lsd.free_blocks && !lsd.bad_blocks) ||
inode.i_flags & EXT4_INLINE_DATA_FL) {
if (num_delarray >= max_delarray) {
max_delarray += 50;
diff --git a/lib/ext2fs/inline_data.c b/lib/ext2fs/inline_data.c
index 7a81da0..f318b41 100644
--- a/lib/ext2fs/inline_data.c
+++ b/lib/ext2fs/inline_data.c
@@ -280,10 +280,9 @@ static errcode_t ext2fs_inline_data_convert_dir(ext2_filsys fs, ext2_ino_t ino,
struct ext2_dir_entry *dir, *dir2;
struct ext2_dir_entry_tail *t;
errcode_t retval;
- unsigned int offset;
+ unsigned int offset, rec_len;
int csum_size = 0;
int filetype = 0;
- int rec_len;
if (EXT2_HAS_RO_COMPAT_FEATURE(fs->super,
EXT4_FEATURE_RO_COMPAT_METADATA_CSUM))
--
1.7.9.7
next prev parent reply other threads:[~2014-05-26 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CFA1367A.A6C68%andreas.dilger@intel.com>
2014-05-20 23:14 ` compile warning on master Andreas Dilger
2014-05-26 6:55 ` Zheng Liu [this message]
2014-05-27 16:56 ` [PATCH] debugfs: fix two warning messages when compiling with LLVM (Re: compile warning on master) Lukáš Czerner
2014-05-27 17:21 ` Theodore Ts'o
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=20140526065508.GA4591@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.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).