Re: Patch to avoid mailboxesdb corruption on concurrent renames

2008-04-04 Thread Ken Murchison
Bron Gondwana wrote: > On Fri, Apr 04, 2008 at 07:10:27AM -0400, Ken Murchison wrote: >> Bron Gondwana wrote: >> >>> Bron ( P.S. isn't it about time for a 2.3.12? I'm getting sick >>>of posting skiplist patches to people running the >>>lastest and having issues! ) >> Yes, it probab

Re: Patch to avoid mailboxesdb corruption on concurrent renames

2008-04-04 Thread Bron Gondwana
On Fri, Apr 04, 2008 at 07:10:27AM -0400, Ken Murchison wrote: > Bron Gondwana wrote: > >> Bron ( P.S. isn't it about time for a 2.3.12? I'm getting sick >>of posting skiplist patches to people running the >>lastest and having issues! ) > > Yes, it probably is. Perhaps I'll make a

Re: Patch to avoid mailboxesdb corruption on concurrent renames

2008-04-04 Thread Ken Murchison
Bron Gondwana wrote: > Bron ( P.S. isn't it about time for a 2.3.12? I'm getting sick >of posting skiplist patches to people running the >lastest and having issues! ) Yes, it probably is. Perhaps I'll make a pre-release today while I troll bugzilla for any showstoppers. -- Ke

Patch to avoid mailboxesdb corruption on concurrent renames

2008-04-03 Thread Bron Gondwana
I've put a header on the patch describing the bug. Basically, the result code from mailbox_open_locked() wasn't being tested sufficiently, and hence the new mailbox name would be created in mailboxes.db even though the files were no longer available to be copied - causing sync bailouts and IOERROR