Re: Problems with timerfd()

From: Andrew Morton
Date: Mon Jul 23 2007 - 02:42:44 EST


On Sun, 22 Jul 2007 23:38:26 -0700 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:

> > Davide has already submitted a patch to you to make read() from a timerfd
> > file descriptor return an 8 byte integer, and I understand it to have been
> > accepted into -mm.
>
> argh. Nobody told me it was an ABI change! We'll need to consider merging
> make-timerfd-return-a-u64-and-fix-the-__put_user.patch into 2.6.22.x as
> well.
>

So I'm trying to write a halfway respectable description of that patch and
I'm stuck when it comes to describing what will happen if someone tries
to run a future timerfd-enabled glibc on 2.2.22 base. In what manner
will it misbehave? What are the consequences of this decision?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/