[Dovecot] imap crash 2.2.9 hg

[Oli Schacher]

Hi Timo

With dovecot built from the latest 2.2.9 hg (342f6962390e) we get imap
crashes. This only affects one account which is used by multiple
clients. The first few logins seem to work ok, but after a few seconds
the log is flooded with


Dec  5 13:43:10 team dovecot: imap-login: Login: user=<sales at example.com>, method=PLAIN, rip=1.2.3.4, lip=5.6.7.8, mpid=27923, TLS, session=<GeNN38jsHgBNbZEi>
Dec  5 13:43:10 team dovecot: imap(sales at example.com): Fatal: master: service(imap): child 27923 killed with signal 11 (core dumped)
Dec  5 13:43:11 team dovecot: imap-login: Login: user=<sales at example.com>, method=PLAIN, rip=1.2.3.4, lip=5.6.7.8, mpid=27925, TLS, session=<NNVS38jsnwBNbZEi>
Dec  5 13:43:11 team dovecot: imap(sales at example.com): Fatal: master: service(imap): child 27925 killed with signal 11 (core dumped)
Dec  5 13:43:11 team dovecot: imap-login: Login: user=<sales at example.com>, method=PLAIN, rip=1.2.3.4, lip=5.6.7.8, mpid=27927, TLS, session=<8LxX38jsAgBNbZEi>
Dec  5 13:43:11 team dovecot: imap(sales at example.com): Fatal: master: service(imap): child 27927 killed with signal 11 (core dumped)
[...]

messagelog meanwile gets floods of:
imap[29173]: segfault at 60 ip 00007f104c160f40 sp 00007fff935a0f58 error 4 in libdovecot-storage.so.0.0.0[7f104c095000+10d000]
imap[29175]: segfault at 60 ip 00007fb7247eff40 sp 00007fff8a949578 error 4 in libdovecot-storage.so.0.0.0[7fb724724000+10d000]
imap[29177]: segfault at 60 ip 00007f59e4f5df40 sp 00007fff70e884b8 error 4 in libdovecot-storage.so.0.0.0[7f59e4e92000+10d000]
imap[29179]: segfault at 60 ip 00007fdda0e68f40 sp 00007fffd3576498 error 4 in libdovecot-storage.so.0.0.0[7fdda0d9d000+10d000]
imap[29181]: segfault at 60 ip 00007f60d774af40 sp 00007fffc249aee8 error 4 in libdovecot-storage.so.0.0.0[7f60d767f000+10d000]
imap[29183]: segfault at 60 ip 00007fce0da4ff40 sp 00007fff33ff92f8 error 4 in libdovecot-storage.so.0.0.0[7fce0d984000+10d000]
imap[29185]: segfault at 60 ip 00007f2e4414ef40 sp 00007fff5888ab28 error 4 in libdovecot-storage.so.0.0.0[7f2e44083000+10d000]
imap[29187]: segfault at 60 ip 00007fb0e6d3ef40 sp 00007fff0ed60c58 error 4 in libdovecot-storage.so.0.0.0[7fb0e6c73000+10d000]
imap[29189]: segfault at 60 ip 00007f77c8292f40 sp 00007fff4d14bc08 error 4 in libdovecot-storage.so.0.0.0[7f77c81c7000+10d000]
imap[29197]: segfault at 60 ip 00007f8366108f40 sp 00007fffd2e060a8 error 4 in libdovecot-storage.so.0.0.0[7f836603d000+10d000]
[...]

The user with the client on ip 1.2.3.4 tells me he doesn't see any
errors in his outlook client, so maybe this crash only affects
additional background connections.

OS: Centos 6.5, 64 bit

(gdb) bt full
#0  0x00007f6fdcb9ef40 in mail_index_view_is_inconsistent () from /usr/lib64/dovecot/libdovecot-storage.so.0
No symbol table info available.
#1  0x00007f6fdcb4f73b in mailbox_is_inconsistent () from /usr/lib64/dovecot/libdovecot-storage.so.0
No symbol table info available.
#2  0x00000000004176dc in client_send_box_error ()
No symbol table info available.
#3  0x0000000000411c46 in cmd_select_full ()
No symbol table info available.
#4  0x0000000000416d6d in command_exec ()
No symbol table info available.
#5  0x0000000000415e90 in ?? ()
No symbol table info available.
#6  0x0000000000415f7d in ?? ()
No symbol table info available.
#7  0x00000000004161fd in client_handle_input ()
No symbol table info available.
#8  0x000000000041656f in client_input ()
No symbol table info available.
#9  0x00007f6fdc87a0c6 in io_loop_call_io () from /usr/lib64/dovecot/libdovecot.so.0
No symbol table info available.
#10 0x00007f6fdc87b187 in io_loop_handler_run () from /usr/lib64/dovecot/libdovecot.so.0
No symbol table info available.
#11 0x00007f6fdc87a038 in io_loop_run () from /usr/lib64/dovecot/libdovecot.so.0
No symbol table info available.
#12 0x00007f6fdc828e43 in master_service_run () from /usr/lib64/dovecot/libdovecot.so.0
No symbol table info available.
#13 0x000000000041fd58 in main ()
No symbol table info available.



Possibly related to recent change 9946079253c4/"imap: If SELECT fails
with "mailbox is inconsistent", disconnect client. (Plus related
cleanups.)" ?

Is this "mailbox_is_inconsistent" call something I need to worry about?
Reverting back to 2.2.7 doesn't show any errors for the affected
account.

Thanks
Oli

-- 
message transmitted on 100% recycled electrons