Messages in this thread | | | Date | Wed, 29 Feb 2012 11:51:49 -0600 | Subject | Re: [PATCH v11 10/12] ptrace,seccomp: Add PTRACE_SECCOMP support | From | Will Drewry <> |
| |
On Wed, Feb 29, 2012 at 11:41 AM, Roland McGrath <mcgrathr@google.com> wrote: > I don't think TIF_NOTIFY_RESUME is apropos here. That only triggers on > returning to user mode, i.e. after syscall exit. But regardless of the > exact implementation details, I don't think it will be prohibitive to add > some means by which the fast-path can back off before actual syscall entry > and go to the slow path for ptrace reporting. > > Since there is no strong reason to think it can't be reorganized that way > later, I don't see any good rationale for constraining the seccomp-filter > feature definition based on a plan to optimize the implementation in the > future.
Sounds good to me. I'll move to ptrace_event and save the problem of code organization for the future.
Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |