* Christian Brauner: > I've been following this a little bit. The kernel version itself doesn't > really mean anything and the kernel version is imho not at all > interesting to userspace applications. Especially for cross-distro > programs. We can't go around and ask Red Hat, SUSE, Ubuntu, Archlinux, > openSUSE and god knows who what other distro what their fixed kernel > version is. And Red Hat Enterprise Linux only has a dozen or two kernel branches under active maintenance, each with their own succession of version numbers. It's just not feasible. Even figuring out the branch based on the kernel version can be tricky! > (Also, as a side-note. I see that you're passing struct rseq *rseq with > a length argument but you are not versioning by size. Is that > intentional? That basically somewhat locks you to the current struct > rseq layout and means users might run into problems when you extend > struct rseq in the future as they can't pass the new struct down to > older kernels. The way we deal with this is now - rseq might preceed > this - is copy_struct_from_user() The kernel retains the pointer after the system call returns. Basically, ownership of the memory area is transferred to the kernel. It's like set_robust_list in this regard.
