qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 00/01] Adding new syscalls to seccomp whitelist


From: Eduardo Otubo
Subject: Re: [Qemu-devel] [PULL 00/01] Adding new syscalls to seccomp whitelist
Date: Fri, 19 Sep 2014 16:38:13 +0200

On Fri, Sep 19, 2014 at 4:15 PM, Peter Maydell <address@hidden> wrote:
> On 19 September 2014 06:22, Eduardo Otubo
> <address@hidden> wrote:
>> The following changes since commit 10e11f4d2bf171f99c6b13883a510acfbc5dd585:
>>
>>   Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging 
>> (2014-09-18 20:02:01 +0100)
>>
>> are available in the git repository at:
>>
>>
>>   git://github.com/otubo/qemu.git tags/goto-upstream
>>
>> for you to fetch changes up to 021db05e6cb0683b12779ff519c7d857620c9e8f:
>>
>>   seccomp: whitelist syscalls fallocate(), fadvise64(), inotify_init1() and 
>> inotify_add_watch() (2014-09-19 14:32:46 +0200)
>>
>> ----------------------------------------------------------------
>> Adding new syscalls to seccomp whitelist: fallocate(), fadvise64(), 
>> inotify_init1() and inotify_add_watch().
>>
>> ----------------------------------------------------------------
>> Philipp Gesang (1):
>>       seccomp: whitelist syscalls fallocate(), fadvise64(), inotify_init1() 
>> and inotify_add_watch()
>>
>>  qemu-seccomp.c | 6 +++++-
>>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> ...how about fixing your compile errors on non-x86 platforms
> before adding more stuff here?

Hm, indeed. I should have double checked that. Thanks for pointing that out.

Philipp, can you fix this, please?

Regards,

-- 
Eduardo Otubo
ProfitBricks



reply via email to

[Prev in Thread] Current Thread [Next in Thread]