Got kernel bug message when using tux ftp server

[Heejoon Park]

I got a wierd Kernel BUG.
Can some body please tell me what's wrong with it ?

tux http server works fine with same environment.

thanks in advance



Oct 18 11:48:23 m5 kernel: <4294742683:net/tux/proto_ftp.c:925>: PASV
accept() returned 0 (state 1). Oct 18 11:48:23 m5 kernel:
<4294742683:net/tux/proto_ftp.c:175>: zapping req 0000010013c3e000's
data socket 0000010012967280. Oct 18 11:48:23 m5 kernel:
<4294742683:net/tux/proto_ftp.c:190>: FTP parser got 10 bytes: --->{LIST
-al^M Oct 18 11:48:23 m5 kernel: }<--- Oct 18 11:48:23 m5 kernel:
<4294742683:net/tux/proto_ftp.c:201>: Newline pos: 8 Oct 18 11:48:23 m5
kernel: <4294742683:net/tux/proto_ftp.c:219>: string val (LIST):
5453494c Oct 18 11:48:23 m5 kernel:
<4294742683:net/tux/proto_ftp.c:407>: parsed LIST. Oct 18 11:48:23 m5
kernel: <4294742683:net/tux/proto_ftp.c:679>: ftp_wait_syn in: data
socket state 3. Oct 18 11:48:23 m5 kernel:
<4294742683:net/tux/proto_ftp.c:692>: ftp_wait_syn out: data socket
state 3. Oct 18 11:48:23 m5 kernel:
<4294742683:net/tux/proto_ftp.c:833>: ftp_do_ls_start(0000010013c3e000,
0). Oct 18 11:48:23 m5 kernel: ----------- [cut here ] --------- [please
bite here ] --------- Oct 18 11:48:23 m5 kernel: Kernel BUG at namei:481
Oct 18 11:48:23 m5 kernel: invalid operand: 0000 [1] Oct 18 11:48:23 m5
kernel: CPU 0 Oct 18 11:48:23 m5 kernel: Modules linked in: tux
zlib_deflate slcm5700 Oct 18 11:48:23 m5 kernel: Pid: 1272, comm: async
IO 0/1 Not tainted 2.6.9-rc3 Oct 18 11:48:23 m5 kernel: RIP:
0010:[<ffffffff80178a75>] <ffffffff80178a75>{link_path_walk+2309}
Oct 18 11:48:23 m5 kernel: RSP: 0018:0000010012715b78  EFLAGS: 00010216
Oct 18 11:48:23 m5 kernel: RAX: 000001001266e7e0 RBX: 0000000000000000
RCX: 000001000174cb90 Oct 18 11:48:23 m5 kernel: RDX: 0000000000000000
RSI: 0000010012715ba0 RDI: 0000010012715b98 Oct 18 11:48:23 m5 kernel:
RBP: 00000000ffffffd8 R08: 0000010011f6fc50 R09: 0000000000000000 Oct 18
11:48:23 m5 kernel: R10: 0000000000000000 R11: ffffffff804ae780 R12:
0000010011f6fc30 Oct 18 11:48:23 m5 kernel: R13: 0000010012715c28 R14:
00000100124f0ed0 R15: 0000000000000001 Oct 18 11:48:23 m5 kernel: FS:
0000002a955702c0(0000) GS:ffffffff804d0e00(0000) knlGS:00000000613e7bb0
Oct 18 11:48:23 m5 kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
000000008005003b Oct 18 11:48:23 m5 kernel: CR2: 0000003b1e64e756 CR3:
0000000000101000 CR4: 00000000000006e0 Oct 18 11:48:23 m5 kernel:
Process async IO 0/1 (pid: 1272, threadinfo 0000010012714000, task
000001001266e7e0) Oct 18 11:48:23 m5 kernel: Stack: ffffffff80490420
000000000000000f 000000069098cabc 0000010012624063
Oct 18 11:48:23 m5 kernel:        00000100018b6ec0 00000100124f0ed0
0000010012624028 0000000000000000
Oct 18 11:48:23 m5 kernel:        0000010013c3e000 0000010012624050
Oct 18 11:48:23 m5 kernel: Call
Trace:<ffffffffa0045675>{:tux:do_dir_line+485}
<ffffffff801afbdb>{do_get_write_access+1243}
Oct 18 11:48:23 m5 kernel:
<ffffffff801b0dc7>{__journal_file_buffer+247}
<ffffffff801a52fa>{ext3_do_update_inode+778}
Oct 18 11:48:23 m5 kernel:        <ffffffff801b05f0>{journal_stop+528}
<ffffffff80130b88>{recalc_task_prio+424}
Oct 18 11:48:23 m5 kernel:        <ffffffff80130c05>{activate_task+101}
<ffffffff80130b88>{recalc_task_prio+424}
Oct 18 11:48:23 m5 kernel:        <ffffffff8035c930>{thread_return+41}
<ffffffffa0026483>{:tux:tux_schedule_atom+163}
Oct 18 11:48:23 m5 kernel:
<ffffffffa00284f1>{:tux:cachemiss_thread+369}
<ffffffff801315e0>{default_wake_function+0}
Oct 18 11:48:23 m5 kernel:
<ffffffff801315e0>{default_wake_function+0}
<ffffffff80111f33>{child_rip+8}
Oct 18 11:48:23 m5 kernel:
<ffffffffa0028380>{:tux:cachemiss_thread+0}
<ffffffff80111f2b>{child_rip+0}
Oct 18 11:48:23 m5 kernel:
Oct 18 11:48:23 m5 kernel:
Oct 18 11:48:23 m5 kernel: Code: 0f 0b 97 08 38 80 ff ff ff ff e1 01 65
48 8b 04 25 18 00 00 Oct 18 11:48:23 m5 kernel: RIP
<ffffffff80178a75>{link_path_walk+2309} RSP <0000010012715b78>