Signed-off-by: Serge Belyshev
---
linux-user/generic/target_resource.h | 1 +
linux-user/syscall.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/linux-user/generic/target_resource.h
b/linux-user/generic/target_resource.h
index f04c93b125..539d8c4677 100644
--- a/linux
Signed-off-by: Serge Belyshev
---
Compile tested, and also verified that target definitions did not change.
linux-user/aarch64/target_resource.h| 1 +
linux-user/alpha/target_resource.h | 21 ++
linux-user/arm/target_resource.h| 1 +
linux-user/cris
Laurent Vivier writes:
>
> Reviewed-by: Laurent Vivier
> Applied to my linux-user-for-7.0 branch.
Thanks!
> perhaps you could also add RLIMIT_RTTIME (15) and update
> target_to_host_resource()?
>
> The next step would be to move the generic definitions to a new file
> in linux-user/generic/t
Laurent Vivier writes:
> ...
>
> According to wait(2), it sounds a little bit more complicated than that.
>
>If WNOHANG was specified in options and there were no children in a
> waitable state, then
>waitid() returns 0 immediately and the state of the siginfo_t
> structure po
Alpha uses different values of some TARGET_RLIMIT_* constants, which were
missing and caused bugs like #577, fixed thus. Also rearranged all three
(alpha, mips and sparc) that differ from everyone else for clarity.
Signed-off-by: Serge Belyshev
Resolves: https://gitlab.com/qemu-project/qemu
When called with WNOHANG and no child has exited, waitid returns with
info.si_pid set to zero and thus check for info.si_pid != 0 will cause
target siginfo structure to be uninitialized. Fixed by removing the check.
Signed-off-by: Serge Belyshev
Resolves: https://gitlab.com/qemu-project/qemu
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1894361
Title:
linux-user: syscall.c lacks pselect6_time64
Status in QEMU:
In Progress
Bug de
Fixed by 0acd4ab849827bbc20402e01c9da088207c0d236 ("linux-user: check
valid address in access_ok()"), fix released in v5.0.0.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ht
Public bug reported:
in commit 50efc69586388a975c1ebd90cb8cc8e4a7328bc4 ("linux-user/riscv:
Update the syscall_nr's to the 5.5 kernel") legacy pselect6 definition
for riscv32 was removed in favour of pselect6_time64, but
pselect6_time64 is not available in syscall.c, thus leaving riscv32
without p
Public bug reported:
qemu-riscv64 version 2.12.93 crashes when mincore() is called with
invalid pointer with the following message:
qemu-riscv64: /opt/qemu/accel/tcg/translate-all.c:2511: page_check_range:
Assertion `start < ((target_ulong)1 << L1_MAP_ADDR_SPACE_BITS)' failed.
qemu:handle_cpu_si
I noticed that this crash is not target specific and it is possible to
reproduce it using qemu-x86_64 with the testcase above
** Summary changed:
- qemu-riscv64 glib hash table crash in qom/object.c
+ qemu linux-user glib hash table crash in qom/object.c
--
You received this bug notification be
Public bug reported:
qemu-riscv64 version 2.11.50 (v2.11.0-2491-g2bb39a657a) crashes running
gcc libgomp.c/sort-1.c testsuite test case with the following message:
(process:11683): GLib-CRITICAL **: g_hash_table_iter_next: assertion
'ri->version == ri->hash_table->version' failed
**
ERROR:qom/o
** Attachment added: "statically linked riscv64 binary executable for the test
case above"
https://bugs.launchpad.net/qemu/+bug/1756519/+attachment/5082075/+files/a.out.xz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
13 matches
Mail list logo
