Problem with redirecting (stack trace).

Hi again,

I apologize for this not doing this earlier. I turned on TUX's debugging
and verbose output options and crashed it again:

May  4 15:48:48 seele01 kernel: invalid operand: 0000
May  4 15:48:48 seele01 kernel: CPU:    0
May  4 15:48:48 seele01 kernel: EIP:    0010:[iput+34/460]    Not tainted
May  4 15:48:48 seele01 kernel: EFLAGS: 00010246
May  4 15:48:48 seele01 kernel: eax: 00000000   ebx: c645a040   ecx:
c645a050   edx: c645a050
May  4 15:48:48 seele01 kernel: esi: cfffb800   edi: 00000000   ebp:
c8d31e6c   esp: c8d31e60
May  4 15:48:48 seele01 kernel: ds: 0018   es: 0018   ss: 0018
May  4 15:48:48 seele01 kernel: Process tux (pid: 596, stackpage=c8d31000)
May  4 15:48:48 seele01 kernel: Stack: c62908e0 c645a040 c14071e0 c8d31e80
c01450e6 c645a040 c9977660 c645a040
May  4 15:48:48 seele01 kernel:        c8d31e9c c0133ef5 c62908e0 c9977660
00000000 00000000 c62908e0 c8d31ec4
May  4 15:48:48 seele01 kernel:        c0132aac c9977660 c9e52440 00000000
c9977660 00000000 c9977660 00000000
May  4 15:48:48 seele01 kernel: Call Trace: [dput+230/356] [fput+209/244]
[filp_close+148/160] [sys_close+93/116] [flush_request+2133/2176]
May  4 15:48:48 seele01 kernel:    [redirect_request+314/323]
[tux_schedule_atom+120/200] [process_requests+328/368]
[event_loop+137/548] [__sys_tux+2222/5624] [sys_write+243/256]
May  4 15:48:48 seele01 kernel:    [system_call+51/56]
May  4 15:48:48 seele01 kernel:
May  4 15:48:48 seele01 kernel: Code: 0f 0b 85 f6 74 03 8b 7e 20 85 ff 74
0d 8b 47 10 85 c0 74 06
May  4 15:48:48 seele01 kernel:  Possibly unexpected TUX-thread exit(11)
at c010741f?
May  4 15:48:48 seele01 kernel: TUX: thread 0 stopping ...
May  4 15:50:06 seele01 kernel: invalid operand: 0000
May  4 15:50:06 seele01 kernel: CPU:    0
May  4 15:50:06 seele01 kernel: EIP:    0010:[iput+34/460]    Not tainted
May  4 15:50:06 seele01 kernel: EFLAGS: 00010246
May  4 15:50:06 seele01 kernel: eax: 00000000   ebx: c629ce00   ecx:
c629ce10   edx: c629ce10
May  4 15:50:06 seele01 kernel: esi: cfffb800   edi: 00000000   ebp:
c8d3fe6c   esp: c8d3fe60
May  4 15:50:06 seele01 kernel: ds: 0018   es: 0018   ss: 0018
May  4 15:50:06 seele01 kernel: Process tux (pid: 597, stackpage=c8d3f000)
May  4 15:50:06 seele01 kernel: Stack: c95558c0 c629ce00 c14071e0 c8d3fe80
c01450e6 c629ce00 c99d53c0 c629ce00
May  4 15:50:06 seele01 kernel:        c8d3fe9c c0133ef5 c95558c0 c99d53c0
00000000 00000000 c95558c0 c8d3fec4
May  4 15:50:06 seele01 kernel:        c0132aac c99d53c0 cc9cf760 00000000
c99d53c0 00000000 c99d53c0 00000000
May  4 15:50:06 seele01 kernel: Call Trace: [dput+230/356] [fput+209/244]
[filp_close+148/160] [sys_close+93/116] [flush_request+2133/2176]
May  4 15:50:06 seele01 kernel:    [redirect_request+314/323]
[tux_schedule_atom+120/200] [process_requests+328/368]
[event_loop+137/548] [__sys_tux+2222/5624] [sys_write+243/256]
May  4 15:50:06 seele01 kernel:    [system_call+51/56]
May  4 15:50:06 seele01 kernel:
May  4 15:50:06 seele01 kernel: Code: 0f 0b 85 f6 74 03 8b 7e 20 85 ff 74
0d 8b 47 10 85 c0 74 06
May  4 15:50:06 seele01 kernel:  Possibly unexpected TUX-thread exit(11)
at c010741f?
May  4 15:50:06 seele01 kernel: TUX: thread 1 stopping ...
May  4 15:50:06 seele01 kernel: PRINT req cf8b2000 <c023953b>, sock
00000000
May  4 15:50:06 seele01 kernel: ... idx: 0
May  4 15:50:06 seele01 kernel: ... meth:{<null>}, uri:{<null>},
query:{<null>}, ver:{<null>}
May  4 15:50:06 seele01 kernel: ... post_data:{<NULL>}(0).
May  4 15:50:06 seele01 kernel: ... headers: {<NULL>}
May  4 15:50:06 seele01 kernel: PRINT req cf891000 <c023953b>, sock
00000000
May  4 15:50:06 seele01 kernel: ... idx: 0
May  4 15:50:06 seele01 kernel: ... meth:{<null>}, uri:{<null>},
query:{<null>}, ver:{<null>}
May  4 15:50:06 seele01 kernel: ... post_data:{<NULL>}(0).
May  4 15:50:06 seele01 kernel: ... headers: {<NULL>}

Last two chunks of message repeat until the machine is rebooted.

I'm spending some time looking into it myself, but I don't think I know
enough to figure this out.

-Alan