Dispatcher - single line output (perl)

[Leigh Purdie]

On 5/25/06, Valdis.Kletnieks at vt.edu <Valdis.Kletnieks at vt.edu> wrote:
> On Wed, 24 May 2006 11:26:08 +1000, Leigh Purdie said:
>
> > Note the 228387 four from the top, and also after the 228390's.
> >
> > Is this something that should be considered a bug? If so (and it's
> > likely to be fixed in RHEL4 in the near future), then I'll be able to
> > greatly simplify the dispatcher code. :)
>
> This smells a lot like a missing lock on an SMP or preemtable kernel. I'm not
> thrilled about having to grab a lock before the first call to audit_log_start
> and leaving it locked till the final audit_log_end for the event, since it
> could easily be 4 or 5 start/end pairs to get all of it out.

Should be safe to rule out SMP. I'm running on a uni-processor, AMD64
(no hyperthreading) with an i686 kernel:

$ uname -a
Linux rhel4 2.6.9-34_snare.EL #1 Sat Apr 8 23:19:35 EST 2006 i686
athlon i386 GNU/Linux

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 31
model name      : AMD Athlon(tm) 64 Processor 3200+
stepping        : 0
cpu MHz         : 2001.031
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext
3dnow
bogomips        : 4012.44

L.