Upas/fs and imap4d bug

Upas/fs and imap4d bug

[sirjofri+ml-9front]

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

Re: Upas/fs and imap4d bug (fixed)

[sirjofri+ml-9front]

Hey all,

> [Subject line]

just for information: this bug was fixed yesterday! Thank you very much, 
ori

Sent from FairEmail (which is an excellent Android mail client) via my 
9front smtpd as an answer to a mail I pulled via 9front imap4d in a 
folder.

sirjofri

Upas/fs and imap4d bug

[sirjofri+ml-9front]

Hello all,

Weeks ago I already got imap4d errors. I then rolled back to the older 
version (before upas changes to new date lib) and it worked fine again.

Now I updated my system and the bug still occurs. Here is an excerpt from 
my /sys/log/imap4d:

oat Oct 17 20:04:05 185.100.87.246!57794 tls reports failed: i/o on 
hungup channel
oat Oct 17 20:06:10 185.100.87.246!50254 tls reports failed: devtls 
expected ver=303, saw (len=8239) type=47 ver=4554 'GET /�����PϚ'
oat Oct 18 10:31:15 107.6.171.130!35816 tls reports failed: i/o on hungup 
channel
oat Oct 19 18:35:05 193.37.255.114!36020 tls reports failed: devtls 
expected ver=303, saw (len=34) type=1 ver=2 '�%'
oat Oct 19 18:35:05 193.37.255.114!36324 tls reports failed: no matching 
cipher suite
oat Oct 19 18:35:05 193.37.255.114!36342 tls reports failed: no matching 
cipher suite
oat Oct 19 19:41:50 192.241.234.16!37832 tls reports failed: i/o on 
hungup channel
oat Oct 19 23:32:33 193.142.146.50!64503 tls reports failed: devtls 
expected ver=303, saw (len=12074) type=3 ver=0 ''
oat Oct 20 01:08:14 87.251.75.21!58124 tls reports failed: devtls 
expected ver=303, saw (len=11046) type=3 ver=0 ''
oat Oct 20 09:29:58 164.68.112.178!57559 tls reports failed: i/o on 
hungup channel
oat Oct 21 05:27:59 183.134.104.149!54207 tls reports failed: i/o on 
hungup channel
oat Oct 21 05:38:31 89.248.169.12!39934 tls reports failed: i/o on hungup 
channel
upas/fs: user: sirjofri; note: sys: trap: fault write addr=0x0 
pc=0x219050
fs 4591335: suicide: sys: trap: fault write addr=0x0 pc=0x219050
oat Oct 21 14:01:12 192.241.237.171!54876 tls reports failed: i/o on 
hungup channel
oat Oct 22 09:01:02 142.93.153.132!52684 tls reports failed: Hangup
oat Oct 22 09:01:02 142.93.153.132!53364 tls reports failed: devtls 
expected ver=303, saw (len=8239) type=47 ver=4554 'GET /������ޣ'
oat Oct 22 19:26:52 178.128.165.19!43250 tls reports failed: devtls 
expected ver=303, saw (len=8239) type=47 ver=4554 'GET /����'

It seems to be some upasfs bug combined with missing cipher and/or bad 
characters/unicode stuff.

I could try give more data on this issue.

sirjofri