Ingo Molnar writes:
> * Eric W. Biederman wrote:
>
>> Ingo Molnar writes:
>>
>> > * Eric W. Biederman wrote:
>> >
>> >> The trouble with attributes is that means you can't filter your system
>> >> call arguments with seccomp. [
Ingo Molnar writes:
> * Eric W. Biederman wrote:
>
>> The trouble with attributes is that means you can't filter your system
>> call arguments with seccomp. [...]
>
> There's nothing keeping seccomp from securely fetching those arguments and
> extendin
Ingo Molnar writes:
> * Arnd Bergmann wrote:
>
>> However, the other question that has to be asked then is whether
>> there is anything wrong with wait4()/waitid() and getrusuage() that
>> we want to change beyond the time value passing. We have
>> answered a similar question with 'yes' for
Arnd Bergmann <a...@arndb.de> writes:
> On Thu, Apr 19, 2018 at 5:20 PM, Arnd Bergmann <a...@arndb.de> wrote:
>> On Thu, Apr 19, 2018 at 4:59 PM, Eric W. Biederman <ebied...@xmission.com>
>> wrote:
>>> I suspect you want to use __kernel_ulong
Arnd Bergmann writes:
> Most architectures now use the asm-generic copy of the sysvipc data
> structures (msqid64_ds, semid64_ds, shmid64_ds), which use 32-bit
> __kernel_time_t on 32-bit architectures but have padding behind them to
> allow extending the type to 64-bit.
>
>
Arnd Bergmann writes:
> We have several files on sparc that include linux/compat.h and expect
> asm/compat.h not to be included, otherwise we get a build failure.
Should this say: "We have several files on sparc that include
linux/compat.h and expect asm/compat.h not be included
Paul Eggert writes:
> On 11/27/2017 09:00 AM, Arnd Bergmann wrote:
>> b) Extend the approach taken by the x32 ABI, and use the 64-bit
>> native structure layout for rusage on all architectures with new
>> system calls that is otherwise compatible. A possible problem