kernel BUG at fs.c:567

kernel BUG at fs.c:567

[Stephen Crowley]

kernel 2.4.0-test10-pre6, but this has been here as long as I can
remember.

starting wine triggers the bug, C: points to /win2k which is an NTFS
filesystem.

The offending code..

/* It's fscking broken. */
        
static int ntfs_get_block(struct inode *inode, long block, struct buffer_head *bh, int create)
{
        BUG();
        return -1;
}
		
Heh. is there something else can be done there instead of just taking a crap
on itself? I can no longer read anything from /proc after this happens.

Oct 28 18:27:54 intolerance kernel: kernel BUG at fs.c:567!
Oct 28 18:27:54 intolerance kernel: invalid operand: 0000
Oct 28 18:27:54 intolerance kernel: CPU:    0
Oct 28 18:27:54 intolerance kernel: EIP:    0010:[ntfs_get_block+20/32]
Oct 28 18:27:54 intolerance kernel: EFLAGS: 00210282
Oct 28 18:27:54 intolerance kernel: eax: 00000018   ebx: cc95e2c0   ecx: c6bc2000   edx: cf974520
Oct 28 18:27:54 intolerance kernel: esi: 00000000   edi: 0000000b   ebp: 00000800   esp: c6bc3dfc
Oct 28 18:27:54 intolerance kernel: ds: 0018   es: 0018   ss: 0018
Oct 28 18:27:54 intolerance kernel: Process wine (pid: 1502, stackpage=c6bc3000)
Oct 28 18:27:54 intolerance kernel: Stack: c0215e52 c0216278 00000237 c012f904 c70f7340 00000000 cc95e2c0 00000000 
Oct 28 18:27:54 intolerance kernel:        00000000 c11c6170 00000000 c70f73dc 00000000 00000000 00000000 cc95e2c0 
Oct 28 18:27:54 intolerance kernel:        000002a4 c70f7340 00000000 c0122263 c11c6170 c11c6170 c1480eb4 00000000 
Oct 28 18:27:54 intolerance kernel: Call Trace: [tvecs+44350/74220] [tvecs+45412/74220] [block_read_full_page+236/488] [add_to_p age_cache_unique+267/280] [ntfs_readpage+15/20] [ntfs_get_block+0/32] [read_cluster_nonblocking+258/324] 
Oct 28 18:27:54 intolerance kernel:        [filemap_nopage+304/776] [filemap_nopage+0/776] [do_no_page+80/176] [handle_mm_fault+ 231/340] [do_page_fault+315/992] [do_page_fault+0/992] [old_mmap+192/240] [old_mmap+224/240] 
Oct 28 18:27:54 intolerance kernel:        [error_code+52/60] 
Oct 28 18:27:54 intolerance kernel: Code: 0f 0b 83 c4 0c b8 ff ff ff ff c3 90 8b 44 24 08 68 90 fb 14 


Please CC: responses, I'm not subscribed to the list.

-- 
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: kernel BUG at fs.c:567

[David Weinehall]

On Sat, Oct 28, 2000 at 06:43:42PM -0500, Stephen Crowley wrote:
> kernel 2.4.0-test10-pre6, but this has been here as long as I can
> remember.
> 
> starting wine triggers the bug, C: points to /win2k which is an NTFS
> filesystem.

[snip]

Yep, there's a solution for this. Get yourself the complete
specifications for the Win2K NTFS, and implement it. The kernel NTFS
simply doesn't support the Win2K NTFS, and rather than risking anything,
it just OOPS:es. Not that I have any Win2K systems, but if I had, I'd
damn sure rather see the kernel OOPS than those filesystems trashed.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: kernel BUG at fs.c:567

[Stephen Crowley]

On Sun, Oct 29, 2000 at 11:27:58AM +0100, David Weinehall wrote:
> On Sat, Oct 28, 2000 at 06:43:42PM -0500, Stephen Crowley wrote:
> > kernel 2.4.0-test10-pre6, but this has been here as long as I can
> > remember.
> > 
> > starting wine triggers the bug, C: points to /win2k which is an NTFS
> > filesystem.
>
> Yep, there's a solution for this. Get yourself the complete
> specifications for the Win2K NTFS, and implement it. The kernel NTFS
> simply doesn't support the Win2K NTFS, and rather than risking anything,
> it just OOPS:es. Not that I have any Win2K systems, but if I had, I'd
> damn sure rather see the kernel OOPS than those filesystems trashed.

I see.. but the FS is mounted read-only, so even if it didn't oops why would
there be a risk of it getting trashed? I really wouldn't mind if it did got
trashed.. thanks for the pointer though.

-- 
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/