> [...] Could you please split all these totally different cases into
> separate syscalls instead?
sure, i'm all for it, but in a different pass, and after syncing up with
glibc. An API cleanup like this should have been done upon the
introduction of futexes, why didnt you comment on this then? Splitting off
FUTEX_REQUEUE in isolation is quite pointless.
> > + case FUTEX_REQUEUE:
> > + pos_in_page2 = uaddr2 % PAGE_SIZE;
> > +
> > + /* Must be "naturally" aligned */
> > + if (pos_in_page2 % sizeof(u32))
> > + return -EINVAL;
>
> Who guarantess that the alignment of u32 is always the same as it's size?
glibc. We do not want to handle all the misaligned cases for obvious
reasons. The use of u32 (instead of a native word) is a bit unfortunate on
64-bit systems but now a reality.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/