> I tried to decode the disassembly, got lots of it done,
> but I bogged down on something that may be outside of the
> NTFS realm. I have ALL kernel hacking options enabled
> (=y), and it's a bit hairy (for me) to decode all of the
> extra/added code, and this may be where the oops is
> happening. Dunno really, just wanted to warn you.
This was one of the issues I suspected (lots of hacking option) and
asked for .config also. Your __ntfs_init_inode was *huge* and the oops
Code didn't resembled to any of written in __ntfs_init_inode ...
unless you have some hardware issue (bit flips, memory/CPU, etc). When
I have time I'll also take a closer look. I don't exclude some
alignment issues either ...
Szaka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/