From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from oat.nine.sirjofri.de ([5.45.105.127]) by ewsd; Fri Oct 23 08:24:58 -0400 2020
Received: from sirjofri.de ([94.222.62.23]) by oat; Fri Oct 23 14:24:02 +0200 2020
Date: Fri, 23 Oct 2020 12:24:37 +0000 (UTC)
From: sirjofri+ml-9front@sirjofri.de
To: 9front@9front.org
Message-ID: <10d667a9-9c18-4675-92eb-03cebb1d72e8@sirjofri.de>
Subject: Upas/fs and imap4d bug
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Correlation-ID: <10d667a9-9c18-4675-92eb-03cebb1d72e8@sirjofri.de>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: database hosting shader 

Hello,

I have additional information about this bug.

First, I noticed the bug only occurs with my separate mailbox folders. In 
my setup I have the standard mbox as well as ml-9front and ml-9fans (for 
the mailing lists). Imap works for my standard mbox, but new messages in 
the other folders don't show up on my client.

Also I ran acid on the systrap upas/fs process. Here again the lines from 
the log:

upas/fs: user: sirjofri; note: sys: trap: fault write addr=0x0 
pc=0x219050
fs 4591335: suicide: sys: trap: fault write addr=0x0 pc=0x219050

And the amd64 acid lstk():

strcmp(s2=0x21daa8)+0x0 /sys/src/libc/port/strcmp.c:5
removembox+0x32 /sys/src/cmd/upas/fs/mbox.c:302

This bug occured between Oct 21 05:38:31 and Oct 21 14:01:12. I'll try 
reading the code and provide some fix for this. I think this is not 
related to the general imap bug that mails don't show up, but preventing 
suicide traps is good.

sirjofri