Did that, got lots of output, but the oops isn't reproducible
AFAIK, so I haven't collected all of that debug output.
>> > > Then mount and to the directory changes. Assuming that you get the bug
>> again could you send me the captured kernel log output? (Note there
>> will be massive amounts of output.)
>> > >
>> > > The code looks ok and I can't reproduce here so it would be helpful to
>> see if there are any oddities on your partition. Just to make sure it
>> is not the compiler, could you do a "make fs/ntfs/inode.S" and send me
>> that as well?
The .config file, gcc -v output, and /proc/cpuinfo are added as
objdump disassembly and make fs/ntfs/inode.s files are also
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/