Skip to contentSkip to conversation

CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK

2.6.28.x FIX Tomáš Szépe 2 participants 4 messages Jun 11, 2009

lore
Share & tools
lore
#0 lore raw

Hello,

Fix: CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK. Patch against 2.6.28.10.

inlined please find a trivial fix that makes it possible to run complete systems out of an initramfs on 2.6.28.10 again (this broke somewhere between 2.6.27 and 2.6.28).

Signature · 35 lines
Tomáš Szépe <[email protected]>

diff -urN a/fs/Kconfig b/fs/Kconfig
--- a/fs/Kconfig	2008-12-25 00:26:37 +0100
+++ b/fs/Kconfig	2009-06-11 04:23:12 +0200
@@ -172,14 +172,6 @@
 	bool
 	default n
 
-config FILE_LOCKING
-	bool "Enable POSIX file locking API" if EMBEDDED
-	default y
-	help
-	  This option enables standard file locking support, required
-          for filesystems like NFS and for the flock() system
-          call. Disabling this option saves about 11k.
-
 source "fs/xfs/Kconfig"
 source "fs/gfs2/Kconfig"
 
@@ -270,6 +262,14 @@
 
 endif # BLOCK
 
+config FILE_LOCKING
+	bool "Enable POSIX file locking API" if EMBEDDED
+	default y
+	help
+	  This option enables standard file locking support, required
+          for filesystems like NFS and for the flock() system
+          call. Disabling this option saves about 11k.
+
 config DNOTIFY
 	bool "Dnotify support"
 	default y
#1 lore raw
Quoted 8 lines · Tomáš Szépe

Hello,

Fix: CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK. Patch against 2.6.28.10.

inlined please find a trivial fix that makes it possible to run complete systems out of an initramfs on 2.6.28.10 again (this broke somewhere between 2.6.27 and 2.6.28).

2.6.28 is no longer supported, sorry.

Is this an issue in 2.6.29 or 2.6.30?

thanks,

greg k-h

#2 lore raw
Quoted 9 lines
Quoted 6 lines

Fix: CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK. Patch against 2.6.28.10.

inlined please find a trivial fix that makes it possible to run complete systems out of an initramfs on 2.6.28.10 again (this broke somewhere between 2.6.27 and 2.6.28).

2.6.28 is no longer supported, sorry.
Is this an issue in 2.6.29 or 2.6.30?

Yes. I also sent a patch (in a separate email) that applies on 2.6.29.x, 2.6.30.x, and current git master branch head.

Best regards,

Signature · 1 line
Tomáš Szépe <[email protected]>
#3 lore raw
Quoted 7 lines · Tomáš Szépe
Quoted 7 lines
Quoted 6 lines

Fix: CONFIG_FILE_LOCKING should not depend on CONFIG_BLOCK. Patch against 2.6.28.10.

inlined please find a trivial fix that makes it possible to run complete systems out of an initramfs on 2.6.28.10 again (this broke somewhere between 2.6.27 and 2.6.28).

Quoted 5 lines
Quoted 2 lines

2.6.28 is no longer supported, sorry.
Is this an issue in 2.6.29 or 2.6.30?

Yes. I also sent a patch (in a separate email) that applies on 2.6.29.x, 2.6.30.x, and current git master branch head.

Ah, ok, I see that now, sorry for getting ahead.

greg k-h