I'm not sure how extensively the RCU code is used (it looks like not
much), but I don't think this bug is fixable without disabling it, or at
least getting rid of the RCU thread in cases where the emulated process
is not multithreaded.
--
You received this bug notification because you are a membe
I mentioned the timeout options (send/receive timeout) which are the
ones I was interested in.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1075339
Title:
linux-user emulation of setsockopt ignore
Public bug reported:
setsockopt always treats the argument as a 4-byte int. This breaks
timeout options (for which it's an 8- or 16-byte timeval structure,
depending on word size) and possibly other socket options. int is
probably a safe default, but options whose values are other types need
speci
Public bug reported:
linux-user/syscall.c's do_socket function contains socket type remapping
to work around the nonsensically-permuted MIPS socket types. However, it
fails to account for the SOCK_NONBLOCK and SOCK_CLOEXEC flags that may
be or'd onto the type. Thus, a call from the application suc
I accidentally posted the patch, which is here, on the wrong bug report
(1068900 instead of here). Apologies. For reference here is the patch;
it was committed and fixes this issue:
https://lists.eait.uq.edu.au/pipermail/microblaze-
linux/2012-October/005760.html
Issue # 1068900, where I mistaken
Arg, somehow I added the above comment on the wrong bug. Thus bug is not
fixed. The other bug report I recently filed was fixed.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1068900
Title:
Thread
Patch for the issue is available here:
https://lists.eait.uq.edu.au/pipermail/microblaze-
linux/2012-October/005760.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1068900
Title:
Thread cancell
Public bug reported:
Thread cancellation (and certain other implementation-internal things
such as set*id() and timers) are implemented in userspace on Linux by
stealing a couple of the realtime signals for internal use by the
implementation, leaving them unavailable to applications. Unfortunately
Here is a minimal test case showing the problem.
** Attachment added: "minimal test case"
https://bugs.launchpad.net/qemu/+bug/1066909/+attachment/3399581/+files/badclone.s
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https:/
Public bug reported:
When CLONE_THREAD is used, the new process starts with the program
counter pointing to the system call instruction, rather than the
instruction immediately following it. This causes an infinite cascade
(linear growth, not exponential) of thread creation, which quickly
crashes
10 matches
Mail list logo
