TUX kernel panic - directory for log file doesn't exist...?

[Kyrian <kyrian@xxxxxxx>]

All,

If indeed there is anyone alive on here, I've just found out something 
'interesting'...

If you are dumb enough (hey, I was in a hurry ;-) to start up TUX 
without a directory existing in which to write to its log file (pretty 
certainly different to just having a missing logfile in kernel terms), 
it starts up, with a warning of (edited for security, of course):

Jun 14 15:25:50 XYZ kernel: TUX: logger thread started.
Jun 14 15:25:50 XYZ kernel: TUX: could not open log file 
{ABC.../access_log_tux}!
Jun 14 15:25:50 XYZ kernel: TUX: thread 0 listens on http://X.Y.Z.K:80.

It then goes on to work just fine, but when you try and stop it again, 
you get a kernel panic, as follows.

Anyways, I just thought it might be a better idea to have TUX fail to 
start if it can't find a log file, rather than crash the machine out 
with a kernel panic when you try and stop it. Or of course the 
underlying problem could be fixed.

K.

Jun 15 02:45:24 XYZ kernel: TUX: thread 0 stopping ...
Jun 15 02:45:24 XYZ kernel: Unable to handle kernel NULL pointer dereference
at virtual address 00000020
Jun 15 02:45:24 XYZ kernel:  printing eip:
Jun 15 02:45:24 XYZ kernel: f8a9fbef
Jun 15 02:45:24 XYZ kernel: *pde = 00000000
Jun 15 02:45:24 XYZ kernel: Oops: 0002 [#1]
Jun 15 02:45:24 XYZ kernel: last sysfs file: /block/hda/hda1/size
Jun 15 02:45:24 XYZ kernel: Modules linked in: ip_conntrack_netbios_ns 
xt_state ip_conntrack nfnetlink iptable_filter ip_tables tux 
zlib_deflate ipv6 autofs4 hidp rfcomm l2cap bluetooth sunrpc ipt_LOG 
ipt_REJECT xt_tcpudp x_tables dm_mirror dm_mod video button battery ac 
lp parport_pc parport floppy nvram 8139too 8139cp mii i2c_i810 
i2c_algo_bit i2c_i801 i2c_core uhci_hcd ehci_hcd raid1 ext3 jbd
Jun 15 02:45:24 XYZ kernel: CPU:    0
Jun 15 02:45:24 XYZ kernel: EIP:    0060:[<f8a9fbef>]    Not tainted VLI
Jun 15 02:45:24 XYZ kernel: EFLAGS: 00010246   (2.6.16-1.2096_FC5 #1)
Jun 15 02:45:24 XYZ kernel: EIP is at tux_flush_workqueue+0x68/0xd3 [tux]
Jun 15 02:45:24 XYZ kernel: eax: 00000000   ebx: f7289800   ecx: 
f8ab8168   edx: f1891000
Jun 15 02:45:24 XYZ kernel: esi: f8ab7fc0   edi: f8ab8158   ebp: 
00000000   esp: f03beaac
Jun 15 02:45:24 XYZ kernel: ds: 007b   es: 007b   ss: 0068
Jun 15 02:45:24 XYZ kernel: Process tux (pid: 1856, threadinfo=f03be000 
task=f1891000)
Jun 15 02:45:24 XYZ kernel: Stack: <0>f8ab8134 f8ab8134 f8ab7fc0 
00000000 f8aa933b 00000002 f8ab8080 f8ab8110
Jun 15 02:45:24 XYZ kernel:        00000000 f8ab7fc0 f8aaa647 c02dd5cd 
c02dc257 e8af7000 00000009 f1891128
Jun 15 02:45:24 XYZ kernel:        f6853550 5d013800 003d2e12 00000000 
d0f43000 c02dd5cd 003d0900 00000000
Jun 15 02:45:24 XYZ kernel: Call Trace:
Jun 15 02:45:24 XYZ kernel:  [<f8aa933b>] flush_all_requests+0x5d/0xa1 [tux]
   [<f8aaa647>] __sys_tux+0x809/0x1101 [tux]
Jun 15 02:45:24 XYZ kernel:  [<c02dd5cd>] _spin_unlock_irq+0x5/0x7     
[<c02dc257>] schedule+0x4a1/0x4ff
Jun 15 02:45:24 XYZ kernel:  [<c02dd5cd>] _spin_unlock_irq+0x5/0x7     
[<f8aaaf2f>] __sys_tux+0x10f1/0x1101 [tux]
Jun 15 02:45:24 XYZ kernel:  [<c013e2a8>] get_page_from_freelist+0x6f/0x2db
  [<c013e2a8>] get_page_from_freelist+0x6f/0x2db
Jun 15 02:45:24 XYZ kernel:  [<c01c1672>] _atomic_dec_and_lock+0x22/0x2c
[<c013e57a>] __alloc_pages+0x66/0x26c
Jun 15 02:45:24 XYZ kernel:  [<c02dd5ab>] _read_unlock_irq+0x5/0x7     
[<c013a370>] find_get_page+0x39/0x3f
Jun 15 02:45:24 XYZ kernel:  [<c013c7ab>] filemap_nopage+0x165/0x2ea     
[<c0144aac>] __handle_mm_fault+0x41d/0x7c3
Jun 15 02:45:24 XYZ kernel:  [<c011df67>] do_exit+0x19e/0x6c8     
[<c011e515>] sys_exit_group+0x0/0xd
Jun 15 02:45:24 XYZ kernel:  [<c0102be9>] syscall_call+0x7/0xb    
<0>Code: 0f 0b a7 00 54 de aa f8 8b 02 39 50 04 74 08 0f 0b a8 00 54 de 
aa f8 89 48 04 89 01 89 12 89 52 04 89 f8 e8 dc d9 83 c7 8b 43 6c <c7> 
40 20 00 00 00 00 c7 40 24 00 00 00 00 c7 43 04 00 00 00 00
Jun 15 02:45:24 XYZ kernel: Continuing in 120 seconds. ^MContinuing in 
119 seconds. ^MContinuing in 118 seconds.
[ etc. with random intervals of seconds ]
Jun 15 02:45:24 XYZ kernel:  <0>Fatal exception: panic in 5 seconds

_______________________________________________

tux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/tux-list