[DragonFlyBSD - Bug #3318] Segmenation fault when a process resumed with checkpt exits
Issue #3318 has been updated by zabolekar.
tuxillo wrote in #note-1:
> We'll try t at least handle that case but we're also considering how useful
> process checkpointing really is. If anybody has any feedback about it now it
> would be the time to share it :-)
To clarify, I don't actually have a use for process checkpointing yet, this was
my first time experimenting with it. It's just that sys_checkpoint/checkpt
looks so nice and boilerplate-free compared to e.g. CRIU :)
Bug #3318: Segmenation fault when a process resumed with checkpt exits
http://bugs.dragonflybsd.org/issues/3318#change-14387
* Author: zabolekar
* Status: In Progress
* Priority: Normal
* Assignee: tuxillo
* Target version: 6.4
* Start date: 2022-06-12
DragonFly version: 6.2.1
Code example (error handling omitted for brevity):
#include
#include
#include
#include
void save(const char* filename)
{
int file = open(filename, O_RDWR|O_CREAT|O_TRUNC, 0666);
sys_checkpoint(CKPT_FREEZE, file, -1, -1);
close(file);
}
int main()
{
puts("a");
save("a.ckpt");
puts("b");
}
Expected output:
% gcc test.c -o test -Wall -Wextra
% ./test
a
b
% checkpt -r a.ckpt
b
Actual output:
% gcc test.c -o test -Wall -Wextra
% ./test
a
b
% checkpt -r a.ckpt
b
pid 1143 (test), uid 1001: exited on signal 11 (core dumped)
Segmentation fault (core dumped)
Backtrace with @gdb test test.core@:
#0 0x00080040400f in __tls_get_addr () from /libexec/ld-elf.so.2
#1 0x00080075648a in _thread_finalize () from /lib/libc.so.8
#2 0x000800756449 in exit () from /lib/libc.so.8
#3 0x004007b3 in _start ()
See also: https://lists.dragonflybsd.org/pipermail/users/2022-June/405002.html
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #1921] we miss mlockall
Issue #1921 has been updated by tuxillo. Still pending of doing the the rlimit work, this is a reminder to myself. Bug #1921: we miss mlockall http://bugs.dragonflybsd.org/issues/1921#change-14386 * Author: alexh * Status: In Progress * Priority: Normal * Assignee: tuxillo * Category: VM subsystem * Target version: 6.4 We don't have the mlockall/munlockall syscalls as documented in [1]. We have at least one tool in base that would benefit from it: cryptsetup. Hopefully someone more familiar with the VM system can implement it without much effort as we already have mlock/munlock. Cheers, Alex Hornung [1]: http://opengroup.org/onlinepubs/007908799/xsh/mlockall.html -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo. Ok, we will have to check route(8) then, there might be a bug that needs fixing there. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14385 * Author: mneumann * Status: In Progress * Priority: Normal * Category: Networking * Target version: 6.4 * Start date: 2022-06-09 After running `dhclient vtnet0`, I cannot ping anything except the default gateway (172.31.1.1). `route show` shows two entries for the default route (172.31.1.1) and one contains *very* strange characters: !clipboard-202206091711-dw2gp.png! (See the second line for 172.31.1.1...) ---Files clipboard-202206091711-dw2gp.png (69.3 KB) clipboard-202206140707-0biu1.png (326 KB) clipboard-202206140730-vzpkc.png (302 KB) clipboard-202206171102-blgae.png (66 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3318] (In Progress) Segmenation fault when a process resumed with checkpt exits
Issue #3318 has been updated by tuxillo.
Status changed from New to In Progress
Assignee set to tuxillo
Target version set to 6.4
Back in the day we added two memory mappable devices (/dev/upmap and
/dev/kpmap) which provide certain data from the kernel without the need of a
system call. See commit:0adbcbd6bc12ddb.
One is per-thread and the other isn't.
The thing is that we need to add handling for the one which isn't per-thread,
since sys_checkpoint(2) and checkpt(1) does not support threaded programs, as
stated in the manpage:
>> Threaded programs cannot currently be checkpointed. The program must be
>> reduced to a single thread before it can be safely checkpointed.
See: https://man.dragonflybsd.org/?command=sys_checkpoint
We'll try t at least handle that case but we're also considering how useful
process checkpointing really is. If anybody has any feedback about it now it
would be the time to share it :-)
Bug #3318: Segmenation fault when a process resumed with checkpt exits
http://bugs.dragonflybsd.org/issues/3318#change-14384
* Author: zabolekar
* Status: In Progress
* Priority: Normal
* Assignee: tuxillo
* Target version: 6.4
* Start date: 2022-06-12
DragonFly version: 6.2.1
Code example (error handling omitted for brevity):
#include
#include
#include
#include
void save(const char* filename)
{
int file = open(filename, O_RDWR|O_CREAT|O_TRUNC, 0666);
sys_checkpoint(CKPT_FREEZE, file, -1, -1);
close(file);
}
int main()
{
puts("a");
save("a.ckpt");
puts("b");
}
Expected output:
% gcc test.c -o test -Wall -Wextra
% ./test
a
b
% checkpt -r a.ckpt
b
Actual output:
% gcc test.c -o test -Wall -Wextra
% ./test
a
b
% checkpt -r a.ckpt
b
pid 1143 (test), uid 1001: exited on signal 11 (core dumped)
Segmentation fault (core dumped)
Backtrace with @gdb test test.core@:
#0 0x00080040400f in __tls_get_addr () from /libexec/ld-elf.so.2
#1 0x00080075648a in _thread_finalize () from /lib/libc.so.8
#2 0x000800756449 in exit () from /lib/libc.so.8
#3 0x004007b3 in _start ()
See also: https://lists.dragonflybsd.org/pipermail/users/2022-June/405002.html
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
