On Jan 10, 2009 16:15 -0500, Theodore Ts'o wrote:
In my experience, there are very few kernel versions and hardware for
which kdump works. I've talked to the people who have to make kdump
work, and every 12-18 months, with a new set of enterprise kernels
comes out, they have to go and fix
On Sat, 2009-01-10 at 04:02 +0100, Andi Kleen wrote:
Long term that problem will hopefully disappear, as gcc learns to do cross
source file inlining (like a lot of other compilers already do)
We've already been able to get GCC doing this for the kernel, in fact
(the --combine -fwhole-program
On Sun, Jan 11, 2009 at 5:11 AM, Andreas Dilger adil...@sun.com wrote:
On Jan 10, 2009 16:15 -0500, Theodore Ts'o wrote:
In my experience, there are very few kernel versions and hardware for
which kdump works. I've talked to the people who have to make kdump
work, and every 12-18 months,
Use the standard magic.h for btrfs and squashfs.
Signed-off-by: Qinghuang Feng qhfeng.ker...@gmail.com
---
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index 0a14b49..7256cf2 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -38,6 +38,7 @@
#include linux/namei.h
#include
On Sun, Jan 11, 2009 at 11:25:32AM -0800, Linus Torvalds wrote:
On Sun, 11 Jan 2009, Andi Kleen wrote:
The proposal was to use -fno-inline-functions-called-once (but
the resulting numbers were not promising)
Well, the _optimal_ situation would be to not need it, because gcc does a
On Sun, 2009-01-11 at 21:14 +0100, Andi Kleen wrote:
On the other hand (my personal opinion, not shared by everyone) is
that the ioctl switch stack issue is mostly only a problem with 4K
stacks and in the rare cases when I still run 32bit kernels
I never set that option because I consider
On Sun, 11 Jan 2009, Andi Kleen wrote:
Was -- i think that got fixed in gcc. But again only in newer versions.
I doubt it. People have said that about a million times, it has never
gotten fixed, and I've never seen any actual proof.
I think that what got fixed was that gcc now at least
Now that btrfs is in mainline, perhaps
a maintainers entry is appropriate?
Perhaps:
diff --git a/MAINTAINERS b/MAINTAINERS
index 6f65a26..138a54c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1021,6 +1021,14 @@ M: m...@bu3sch.de
W: http://bu3sch.de/btgpio.php
S: Maintained
