Your message dated Wed, 27 Nov 2013 15:48:12 +0800
with message-id <8772079.0cH3z6rgsp@brano>
and subject line 
has caused the Debian Bug report #722484,
regarding libdspam7-drv-hash: dspam segfaults [libhash_drv on _hash_drv_seek()]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
722484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722484
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libdspam7-drv-hash
Version: 3.10.1+dfsg-11
Severity: grave
Justification: causes non-serious data loss

Sample of dmesg:
[1701173.909095] dspam[15582]: segfault at 7f8c2197acf8 ip 00007f8c1ea8f69a sp 
00007f8c1cbe9048 error 4 in libhash_drv.so.7.0.0[7f8c1ea8b000+6000]
[1775508.341567] cssclean[25298]: segfault at 7f9b7086a000 ip 0000000000403b5b 
sp 00007fff7d456130 error 7 in cssclean[400000+c000]
[1785820.256253] dspam[8177]: segfault at 7ff586ffe2f8 ip 00007ff58dd4169a sp 
00007ff58cd35048 error 4 in libhash_drv.so.7.0.0[7ff58dd3d000+6000]
[1785862.479249] dspam[8243]: segfault at 7fa456fa62f8 ip 00007fa457fac69a sp 
00007fa4577a1048 error 4 in libhash_drv.so.7.0.0[7fa457fa8000+6000]
[1785888.517082] dspam[8281]: segfault at 7fef8160c2f8 ip 00007fef8261269a sp 
00007fef81e07048 error 4 in libhash_drv.so.7.0.0[7fef8260e000+6000]
[1786011.902307] dspam[8760]: segfault at 7f8a051752f8 ip 00007f8a0617b69a sp 
00007f8a06171048 error 4 in libhash_drv.so.7.0.0[7f8a06177000+6000]

I happened to be in a situation where I can't even fully flush the postfix 
queue without having
Dspam to segfault.
I end up installing dspam-dbg and gdb and attach to the process [I wasn't able 
to run the process
without the init-script].

Here is a stack trace, but sadly libdspam7-drv-hash does not provide debug 
symbols.
(gdb) bt
#0  0x00007ff5afdc369a in _hash_drv_seek () from 
/usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so
#1  0x00007ff5afdc3a19 in _hash_drv_get_spamrecord () from 
/usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so
#2  0x00007ff5afdc3a90 in _ds_get_spamrecord () from 
/usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so
#3  0x00007ff5afdc3cfd in _ds_getall_spamrecords () from 
/usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so
#4  0x00007ff5b28422f6 in _ds_operate () from 
/usr/lib/x86_64-linux-gnu/libdspam.so.7
#5  0x00007ff5b2842e90 in dspam_process () from 
/usr/lib/x86_64-linux-gnu/libdspam.so.7
#6  0x000000000040bad7 in process_message (ATX=ATX@entry=0xd58e90, 
message=message@entry=0xd5aa10, 
    username=username@entry=0xd584e0 "[email protected]", 
result_string=result_string@entry=0x7ff5afdbc348) at dspam.c:540
#7  0x000000000040ce4d in process_users (ATX=ATX@entry=0xd58e90, 
message=message@entry=0xd5af10) at dspam.c:1882
#8  0x000000000040faa0 in process_connection (ptr=0xd56f80) at daemon.c:738
#9  0x00007ff5b2621b50 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007ff5b236ba7d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()



(gdb) bt full
#0  0x00007ff5afdc369a in _hash_drv_seek () from 
/usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so
No symbol table info available.
#1  0x00007ff5afdc3a19 in _hash_drv_get_spamrecord () from 
/usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so
No symbol table info available.
#2  0x00007ff5afdc3a90 in _ds_get_spamrecord () from 
/usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so
No symbol table info available.
#3  0x00007ff5afdc3cfd in _ds_getall_spamrecords () from 
/usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so
No symbol table info available.
#4  0x00007ff5b28422f6 in _ds_operate () from 
/usr/lib/x86_64-linux-gnu/libdspam.so.7
No symbol table info available.
#5  0x00007ff5b2842e90 in dspam_process () from 
/usr/lib/x86_64-linux-gnu/libdspam.so.7
No symbol table info available.
#6  0x000000000040bad7 in process_message (ATX=ATX@entry=0xd58e90, 
message=message@entry=0xd5aa10, 
    username=username@entry=0xd584e0 "[email protected]", 
result_string=result_string@entry=0x7ff5afdbc348) at dspam.c:540
        CTX = 0xd96700
        components = <optimized out>
        copyback = <optimized out>
        have_signature = <optimized out>
        result = <optimized out>
        i = <optimized out>
        internally_canned = 0



-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libdspam7-drv-hash depends on:
ii  libc6      2.13-38
ii  libdspam7  3.10.1+dfsg-11

libdspam7-drv-hash recommends no packages.

libdspam7-drv-hash suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
This error is due to a corrupted CSS file. Teaching dspam to handle this would
require reviewing all the code for libdspam-drv-hash and fix the problem in
multiple place. A better approach is to just run cssclean which has been
enhanced in dspam 3.10.2+dfsg-12 to fix this kind of corruption.

--- End Message ---

Reply via email to