* [9front] upas/fs lstk(), one more time
@ 2023-09-30 21:38 sl
2023-10-01 0:35 ` sl
0 siblings, 1 reply; 6+ messages in thread
From: sl @ 2023-09-30 21:38 UTC (permalink / raw)
To: 9front
finally at a computer. this is complete:
gaff; mail
upas/fs: user: sl; note: sys: trap: fault read addr=0x0 pc=0x2237b0
fs 1389550: suicide: sys: trap: fault read addr=0x0 pc=0x2237b0
upas/nedmail: can't open /mail/fs/ctl: file does not exist: '/mail/fs/ctl'
gaff; acid 1389550
/proc/1389550/text:amd64 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/amd64
acid: lstk()
abort()+0x0 /sys/src/libc/9sys/abort.c:6
sanemsg(m=0x4bdcc8)+0x20 /sys/src/cmd/upas/fs/fs.c:135
parse(mb=0x4382e0,m=0x4bdcc8,addfrom=0x0,justmime=0x1)+0x13 /sys/src/cmd/upas/fs/mbox.c:637
parseattachments(m=0x4bd888,mb=0x4382e0)+0x163 /sys/src/cmd/upas/fs/mbox.c:459
nm=0x4bdcc8
l=0x4bdea0
i=0x4e27a100000001
p=0x4e27a2
x=0x4e27a1
parsebody(m=0x4bd888,mb=0x4382e0)+0x48 /sys/src/cmd/upas/fs/mbox.c:595
nm=0x4e276d
parse(mb=0x4382e0,m=0x4bd888,addfrom=0x0,justmime=0x1)+0x5a /sys/src/cmd/upas/fs/mbox.c:641
parseattachments(m=0x453450,mb=0x4382e0)+0x163 /sys/src/cmd/upas/fs/mbox.c:459
nm=0x4bd888
l=0x4bdc80
i=0x4e279e00000002
p=0x4e27a2
x=0x4e279e
parsebody(m=0x453450,mb=0x4382e0)+0x48 /sys/src/cmd/upas/fs/mbox.c:595
nm=0x4e26e1
parse(mb=0x4382e0,m=0x453450,addfrom=0x0,justmime=0x0)+0x5a /sys/src/cmd/upas/fs/mbox.c:641
cachebody(m=0x453450,mb=0x4382e0)+0x205 /sys/src/cmd/upas/fs/cache.c:372
o=0x20135e00000000
cacheidx(m=0x453450)+0x26 /sys/src/cmd/upas/fs/cache.c:381
ensurecache(m=0x453450,mb=0x4382e0)+0x4d /sys/src/cmd/upas/fs/cache.c:406
pridx0(m=0x453450,b=0x7fffffff69b8,l=0x0,mb=0x4382e0)+0x2f /sys/src/cmd/upas/fs/idx.c:92
pridx(b=0x7fffffff69b8,mb=0x4382e0)+0x62 /sys/src/cmd/upas/fs/idx.c:120
wridxfile(mb=0x4382e0)+0x13b /sys/src/cmd/upas/fs/idx.c:259
buf=0x6f622f6c69616d2f
fd=0x6
b=0xffffbb8800000000
r=0x69616d2f00000000
p=0x438520
n=0x0
d=0x0
syncmbox(mb=0x4382e0,doplumb=0x0)+0x22b /sys/src/cmd/upas/fs/mbox.c:117
a=0x16600000166
n=0x43856000000166
d=0x16600000000
y=0x166
next=0x0
m=0x4794b8
newmbox(r=0x0,path=0x7fffffffecf8,flags=0x0,name=0x4143b8)+0x323 /sys/src/cmd/upas/fs/mbox.c:275
mb=0x4382e0
i=0x2
rv=0x0
l=0x400048
main(argc=0x0,argv=0x7fffffffefa0)+0x1d5 /sys/src/cmd/upas/fs/fs.c:341
mboxfile=0x7fffffffecf8
nodflt=0x400000000
srvpost=0x0
v=0x7fffffffef98
_argc=0x70
_args=0x7fffffffefb7
p=0x500000004
maildir=0x73662f6c69616d2f
mbox=0x6f622f6c69616d2f
srvfile=0x0
_main+0x40 /sys/src/libc/amd64/main9.s:15
acid:
sl
.
w
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] upas/fs lstk(), one more time
2023-09-30 21:38 [9front] upas/fs lstk(), one more time sl
@ 2023-10-01 0:35 ` sl
2023-10-01 1:51 ` Benjamin Purcell
2023-10-01 4:13 ` ori
0 siblings, 2 replies; 6+ messages in thread
From: sl @ 2023-10-01 0:35 UTC (permalink / raw)
To: 9front
i backed up my mbox and added messages back in batches, checking after
each batch that upas/fs was still able to open it. i did this until i
found a specific message upas/fs choked on.
sl
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] upas/fs lstk(), one more time
2023-10-01 0:35 ` sl
@ 2023-10-01 1:51 ` Benjamin Purcell
2023-10-01 4:13 ` ori
1 sibling, 0 replies; 6+ messages in thread
From: Benjamin Purcell @ 2023-10-01 1:51 UTC (permalink / raw)
To: 9front
The suspense is killing me.
On Sat, 30 Sep 2023, at 18:35 UTC-06:00, sl@stanleylieber.com wrote:
> i backed up my mbox and added messages back in batches, checking after
> each batch that upas/fs was still able to open it. i did this until i
> found a specific message upas/fs choked on.
>
> sl
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] upas/fs lstk(), one more time
2023-10-01 0:35 ` sl
2023-10-01 1:51 ` Benjamin Purcell
@ 2023-10-01 4:13 ` ori
2023-10-01 4:20 ` Stanley Lieber
1 sibling, 1 reply; 6+ messages in thread
From: ori @ 2023-10-01 4:13 UTC (permalink / raw)
To: 9front
Quoth sl@stanleylieber.com:
> i backed up my mbox and added messages back in batches, checking after
> each batch that upas/fs was still able to open it. i did this until i
> found a specific message upas/fs choked on.
>
> sl
is it possible to reproduce it with just that message? would
you be comfortable sending it over to someone for debugging?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] upas/fs lstk(), one more time
2023-10-01 4:13 ` ori
@ 2023-10-01 4:20 ` Stanley Lieber
2023-10-01 9:32 ` hiro
0 siblings, 1 reply; 6+ messages in thread
From: Stanley Lieber @ 2023-10-01 4:20 UTC (permalink / raw)
To: 9front
On October 1, 2023 12:13:41 AM EDT, ori@eigenstate.org wrote:
>Quoth sl@stanleylieber.com:
>> i backed up my mbox and added messages back in batches, checking after
>> each batch that upas/fs was still able to open it. i did this until i
>> found a specific message upas/fs choked on.
>>
>> sl
>
>is it possible to reproduce it with just that message? would
>you be comfortable sending it over to someone for debugging?
>
>
unfortunately, the precise message causing the problem turned out to contain sensitive information. i am pretty sure this is the first time upas/fs has refused to index a message for me, but if it happens again, if possible, i'll share the offending malformed message so we can name and shame the villain.
sl
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] upas/fs lstk(), one more time
2023-10-01 4:20 ` Stanley Lieber
@ 2023-10-01 9:32 ` hiro
0 siblings, 0 replies; 6+ messages in thread
From: hiro @ 2023-10-01 9:32 UTC (permalink / raw)
To: 9front
cut the malformed message in halves until you find the part that causes it?
probably those remainders wouldn't be so sensitive ;)
On 10/1/23, Stanley Lieber <sl@stanleylieber.com> wrote:
> On October 1, 2023 12:13:41 AM EDT, ori@eigenstate.org wrote:
>>Quoth sl@stanleylieber.com:
>>> i backed up my mbox and added messages back in batches, checking after
>>> each batch that upas/fs was still able to open it. i did this until i
>>> found a specific message upas/fs choked on.
>>>
>>> sl
>>
>>is it possible to reproduce it with just that message? would
>>you be comfortable sending it over to someone for debugging?
>>
>>
>
> unfortunately, the precise message causing the problem turned out to contain
> sensitive information. i am pretty sure this is the first time upas/fs has
> refused to index a message for me, but if it happens again, if possible,
> i'll share the offending malformed message so we can name and shame the
> villain.
>
> sl
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-10-01 9:36 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-09-30 21:38 [9front] upas/fs lstk(), one more time sl
2023-10-01 0:35 ` sl
2023-10-01 1:51 ` Benjamin Purcell
2023-10-01 4:13 ` ori
2023-10-01 4:20 ` Stanley Lieber
2023-10-01 9:32 ` hiro
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).