[prev in list] [next in list] [prev in thread] [next in thread]
List: hurd-bug
Subject: Re: Backtraces from rumpdisk.static and fdisk when fdisk is called on wd0
From: Samuel Thibault <samuel.thibault () gnu ! org>
Date: 2022-02-16 8:44:28
Message-ID: 20220216084428.4lcamidy6i4mwiux () begin
[Download RAW message or body]
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic