[lkml]   [2018]   [Jan]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 22/22] signal: Unify and correct copy_siginfo_to_user32
Al Viro <> writes:

> On Mon, Jan 15, 2018 at 06:40:09PM -0600, Eric W. Biederman wrote:
>> Among the existing architecture specific versions of
>> copy_siginfo_to_user32 there are several different implementation
>> problems. Some architectures fail to handle all of the cases in in
>> the siginfo union. Some architectures perform a blind copy of the
>> siginfo union when the si_code is negative. A blind copy suggests the
>> data is expected to be in 32bit siginfo format, which means that
>> receiving such a signal via signalfd won't work, or that the data is
>> in 64bit siginfo and the code is copying nonsense to userspace.
> Huh? Negative si_code comes from rt_sigqueueinfo(2); in that case
> the sucker is supposed to pass user-supplied opaque chunk of data
> in ->_sifields._pad. "Copy everything when ->si_code is negative"
> is exactly the right behaviour. Failing to copy it out (and in, for
> copy_siginfo_from_user32()) is a bug.
> 32bit tasks should behave on 64bit host like they would on 32bit one
> when we have biarch compat. And "application using sigqueueinfo() to
> pass data might be using different layouts of the payload" is not
> an excuse for failing to transmit it in the first place.

If glibc actually offered rt_sigqueueinfo or any function that would
queue a full siginfo that would be a compelling argument.

As it is the only users of rt_sigqueueinfo that I am aware of
is CRIU and the implementation of sigqueue.

A couple of months ago I went hunting for users and for anyone who was
defining si_codes and I did not find a single instance of anything
defining signals that would pass more information than is known to
the kernel, and except for CRIU all I found was limited to what
you can do with sigqueue.

So no I do not think my choice will cause a regression.

Further SI_TIMER which the kernel does send is also negative. The
difference between negative and positive is that negative si_codes
are supposed to be signal agnostic and positive si_codes are signal

If this causes a single regression, or if anyone can point me at the
code of an application this will cause a regression for. I will
change the code right then and there.

My concern is that people have not been careful when defining new
signals. What looks like rules in one place are not the rules in
another place. If we had been careful struct siginfo would be the same
on both 32bit and 64bit, and in singalfd. As it is I am battling
accidental redefinitions of SI_USER by the kernel to be something else.

I think it is far more likley that someone will define a signal layout
that needs help going from 64bit to 32bit that my choice not copying all
of the bits will catch, rather than I will break some existing userspace
application. And if we catch it and the siginfo needs translation
because we are not commited to copying everything we can fix it.

Which is a long way of saying I think it would be gravely irresponsible
to just copy all of the bits of struct siginfo when si_code is negative.


 \ /
  Last update: 2018-01-19 22:06    [W:0.218 / U:4.488 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site