Re: Landlock and O_PATH

> Correct, a given Landlock flag/command/attribute will not change 
> behavior over time, as (in theory) all Linux interfaces. If a flag is 
> not enough, extensible structs used by the Landlock syscalls can be 
> used: 
> https://lpc.events/event/7/contributions/657/attachments/639/1159/extensible_syscalls.pdf

That makes sense. One (hopefully) final question: What is Landlock's
policy around future changes in the kernel? Taking the earlier example,
O_PATH was apparently added in Linux 2.6.39. If Landlock had existed
prior to that, and LANDLOCK_ACCESS_FS_WALK as well, would the flag have
been extended to cover that usecase? To be maybe more clear, I'm
wondering if I can trust Landlock policies to always restrict a given
action, irrespective of what new ways to do it may be introduced in
the future?

Thanks,
Mukarram