Re: [PATCH] Fix use-after-free in futex-based semaphore implementations.
[Thread Prev] | [Thread Next]
- Subject: Re: [PATCH] Fix use-after-free in futex-based semaphore implementations.
- From: Ori Bernstein <ori@xxxxxxxxxxxxxx>
- Reply-to: myrddin-dev@xxxxxxxxxxxxxx
- Date: Thu, 14 Mar 2019 00:17:36 -0700
- To: myrddin-dev@xxxxxxxxxxxxxx
- Cc: iriri <iri@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Wed, 13 Mar 2019 01:58:49 -0700, iriri <iri@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > const ulock_wake = {op, uaddr, wakeval > - -> (syscall(Sysulock_wake, a(op), uaddr, a(wakeval)) : int) > + -> (syscall(Sysulock_wake, a(op), uaddr, wakeval) : int) the `a(wakeval)` shouldn't have been removed -- it's an ABI thing: Even 32 bit values go in 64 bit registers on sysv-like platforms. Fixing on my end before committing. -- Ori Bernstein
[PATCH] Fix use-after-free in futex-based semaphore implementations. | iriri <iri@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
- Prev by Date: [PATCH] Fix use-after-free in futex-based semaphore implementations.
- Next by Date: bio.readto and EOF
- Previous by thread: [PATCH] Fix use-after-free in futex-based semaphore implementations.
- Next by thread: bio.readto and EOF
- Index(es):