Blame SOURCES/e2fsprogs-1.42.9-enable-lazy_itable_init-on-newer-kernel-by-default.patch

0ef434
From 165af99c57a686444167fcef56f9fae31d815887 Mon Sep 17 00:00:00 2001
0ef434
From: Lukas Czerner <lczerner@redhat.com>
0ef434
Date: Mon, 24 Feb 2014 18:41:06 +0100
0ef434
Subject: [PATCH 4/8] mke2fs: Enable lazy_itable_init on newer kernel by
0ef434
 default
0ef434
0ef434
Currently is used did not specified lazy_itable_init option we rely on
0ef434
information from ext4 module exported via sysfs interface. However if
0ef434
the ext4 module is not loaded it will not be enabled even though kernel
0ef434
might support it.
0ef434
0ef434
With this commit we set the default according to the kernel version,
0ef434
however we still allow it to be set manually via extended option or be
0ef434
enabled in case that ext4 module advertise that it supports this
0ef434
feature.
0ef434
0ef434
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
0ef434
---
0ef434
 misc/mke2fs.c | 10 +++++++++-
0ef434
 1 file changed, 9 insertions(+), 1 deletion(-)
0ef434
0ef434
diff --git a/misc/mke2fs.c b/misc/mke2fs.c
0ef434
index 76ea60b..23a988e 100644
0ef434
--- a/misc/mke2fs.c
0ef434
+++ b/misc/mke2fs.c
0ef434
@@ -1998,7 +1998,15 @@ profile_error:
0ef434
 			blocksize, sys_page_size);
0ef434
 	}
0ef434
 
0ef434
-	lazy_itable_init = 0;
0ef434
+	/*
0ef434
+	 * On newer kernels we do have lazy_itable_init support. So pick the
0ef434
+	 * right default in case ext4 module is not loaded.
0ef434
+	 */
0ef434
+	if (is_before_linux_ver(2, 6, 37))
0ef434
+		lazy_itable_init = 0;
0ef434
+	else
0ef434
+		lazy_itable_init = 1;
0ef434
+
0ef434
 	if (access("/sys/fs/ext4/features/lazy_itable_init", R_OK) == 0)
0ef434
 		lazy_itable_init = 1;
0ef434
 
0ef434
-- 
0ef434
1.8.3.1
0ef434