[lkml]   [2003]   [Mar]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Linux-NTFS-Dev] ntfs OOPS (2.5.63)
On Thu, 6 Mar 2003 15:34:52 +0100 (MET) Szakacsits Szabolcs <> wrote:

| On Thu, 6 Mar 2003, Anton Altaparmakov wrote:
| > On Thu, 6 Mar 2003, Szakacsits Szabolcs wrote:
| > >
| > > What would be really useful is to disassemble __ntfs_init_inode what I
| > > asked 2 days ago (note, not the above 'make fs/ntfs/inode.S' because
| > > it will not tell what machine code you have on disk), your .config and
| > > exact CPU version (cat /proc/cpuinfo).
| >
| > Yes it will, unless you suspect the assembler [...]
| I suspect everything :) It was also a polite way saying (on a completely
| configured, etc kernel):
| % make fs/ntfs/inode.S
| make: *** No rule to make target `fs/ntfs/inode.S'. Stop.
| Anyway, considering how bogus the oops was and Randy already had two
| oops'es before this NTFS one, I think the NTFS driver was a sufferer
| of other trouble(s) than the originator. So unless one can reproduce
| something close to this one (or Randy sends his first [two] oops), I
| would just trash

I must have missed something here. What other 2 oopses are you referring to?
I understand that other oopses could make a third one bogus, but I didn't
see 2 others. Did I miss them? How did you get that information?
I'll look in the kernel log tonight (at home) to see if I missed them.

As for closing bug reports because they are not reproducible...
sure, people do it, and whoever wants to can close bug reports for that reason,
but you won't catch me doing that. It's a poor reason to close a bug report

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.238 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site