On 04/10/2016 01:46, Kees Cook wrote:
> On Wed, Sep 14, 2016 at 6:19 PM, Andy Lutomirski wrote:
>> On Wed, Sep 14, 2016 at 3:14 PM, Mickaël Salaün wrote:
>>>
>>> On 14/09/2016 20:29, Andy Lutomirski wrote:
On Wed, Sep 14, 2016 at 12:24 AM, Mickaël
On Wed, Sep 14, 2016 at 6:19 PM, Andy Lutomirski wrote:
> On Wed, Sep 14, 2016 at 3:14 PM, Mickaël Salaün wrote:
>>
>> On 14/09/2016 20:29, Andy Lutomirski wrote:
>>> On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wrote:
This third
On Wed, Sep 14, 2016 at 3:14 PM, Mickaël Salaün wrote:
>
> On 14/09/2016 20:29, Andy Lutomirski wrote:
>> On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wrote:
>>> This third origin of hook call should cover all possible trigger paths
>>> (e.g. page fault).
On 14/09/2016 20:29, Andy Lutomirski wrote:
> On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wrote:
>> This third origin of hook call should cover all possible trigger paths
>> (e.g. page fault). Landlock eBPF programs can then take decisions
>> accordingly.
>>
>>
On Wed, Sep 14, 2016 at 12:24 AM, Mickaël Salaün wrote:
> This third origin of hook call should cover all possible trigger paths
> (e.g. page fault). Landlock eBPF programs can then take decisions
> accordingly.
>
> Signed-off-by: Mickaël Salaün
> Cc: Alexei
This third origin of hook call should cover all possible trigger paths
(e.g. page fault). Landlock eBPF programs can then take decisions
accordingly.
Signed-off-by: Mickaël Salaün
Cc: Alexei Starovoitov
Cc: Andy Lutomirski
Cc: Daniel