linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <zhangaihua1@huawei.com>
To: <tytso@mit.edu>, <linux-ext4@vger.kernel.org>
Cc: Aihua Zhang <zhangaihua1@huawei.com>
Subject: [PATCH] fix compile error while opening the macro DOUBLE_CHECK
Date: Tue, 1 Dec 2015 16:58:29 +0800	[thread overview]
Message-ID: <1448960309-27346-1-git-send-email-zhangaihua1@huawei.com> (raw)

From: Aihua Zhang <zhangaihua1@huawei.com>

the error is:
    fs/ext4/mballoc.c:475:43: error: 'struct ext4_group_info' has
no member named 'bb_bitmap'.
    so, the definition of macro DOUBLE_CHECK should before
'struct ext4_group_info', I fixed it, and I moved the macro
AGGRESSIVE_CHECK together, because I think they shoule be together.

Signed-off-by: Aihua Zhang <zhangaihua1@huawei.com>
---
 fs/ext4/ext4.h    |   12 ++++++++++++
 fs/ext4/mballoc.h |   12 ------------
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
index 750063f..04a3732 100644
--- a/fs/ext4/ext4.h
+++ b/fs/ext4/ext4.h
@@ -41,6 +41,18 @@
  */
 
 /*
+ * with AGGRESSIVE_CHECK allocator runs consistency checks over
+ * structures. these checks slow things down a lot
+ */
+#define AGGRESSIVE_CHECK__
+
+/*
+ * with DOUBLE_CHECK defined mballoc creates persistent in-core
+ * bitmaps, maintains and uses them to check for double allocations
+ */
+#define DOUBLE_CHECK__
+
+/*
  * Define EXT4FS_DEBUG to produce debug messages
  */
 #undef EXT4FS_DEBUG
diff --git a/fs/ext4/mballoc.h b/fs/ext4/mballoc.h
index d634e18..3ef1df6 100644
--- a/fs/ext4/mballoc.h
+++ b/fs/ext4/mballoc.h
@@ -23,18 +23,6 @@
 #include "ext4.h"
 
 /*
- * with AGGRESSIVE_CHECK allocator runs consistency checks over
- * structures. these checks slow things down a lot
- */
-#define AGGRESSIVE_CHECK__
-
-/*
- * with DOUBLE_CHECK defined mballoc creates persistent in-core
- * bitmaps, maintains and uses them to check for double allocations
- */
-#define DOUBLE_CHECK__

             reply	other threads:[~2015-12-01  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01  8:58 zhangaihua1 [this message]
2016-03-13 21:19 ` [PATCH] fix compile error while opening the macro DOUBLE_CHECK Theodore Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2015-11-17  3:52 zhangaihua1
2015-11-17  3:04 zhangaihua1
2015-11-17  3:26 ` kbuild test robot
2015-11-17  4:03 ` Greg KH
2015-11-17  6:31   ` Zhang AiHua

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=1448960309-27346-1-git-send-email-zhangaihua1@huawei.com \
    --to=zhangaihua1@huawei.com \
    --cc=linux-ext4@vger.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).