[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Backtraces from rumpdisk.static and fdisk when fdisk is called on wd
From: |
Samuel Thibault |
Subject: |
Re: Backtraces from rumpdisk.static and fdisk when fdisk is called on wd0 |
Date: |
Wed, 16 Feb 2022 09:44:28 +0100 |
User-agent: |
NeoMutt/20170609 (1.8.3) |
Damien Zammit, le mer. 16 févr. 2022 06:33:17 +0000, a ecrit:
> gdb in rumpdisk.static after rumpns_sys_open was called already:
>
> Thread 31 hit Breakpoint 1, 0x08152e40 in rumpns_sys_pread ()
> (gdb) bt
> #0 0x08152e40 in rumpns_sys_pread ()
The question I was asking was not how we end up in rumpns_sys_pread, but
exactly what happens *after* that. How do we end up in the rump driver,
what buffer gets passed, how physical memory allocation is involved etc.
In a word: what happens with the actual memory passed between the IPC
and rump.
Samuel