Re: [PATCH v2 04/10] seccomp: Migrate to use SYSCALL_WORK flag

24.11.2020 20:55, Gabriel Krisman Bertazi пишет: > Dmitry Osipenko writes: > >> Hi, >> >> This patch broke seccomp on arm32 using linux-next, chromium browser >> doesn't work anymore and there are these errors in KMSG: >> >> Unhandled prefetch abort: breakpoint debug exception (0x002) at ... >>

Re: [PATCH v2 04/10] seccomp: Migrate to use SYSCALL_WORK flag

Dmitry Osipenko writes: > Hi, > > This patch broke seccomp on arm32 using linux-next, chromium browser > doesn't work anymore and there are these errors in KMSG: > > Unhandled prefetch abort: breakpoint debug exception (0x002) at ... > > Note that arm doesn't use CONFIG_GENERIC_ENTRY. Please

Re: [PATCH v2 04/10] seccomp: Migrate to use SYSCALL_WORK flag

16.11.2020 20:42, Gabriel Krisman Bertazi пишет: > When one the generic syscall entry code, use the syscall_work field in > struct thread_info and specific SYSCALL_WORK flags to setup this syscall > work. This flag has the advantage of being architecture independent. > > Users of the flag

[PATCH v2 04/10] seccomp: Migrate to use SYSCALL_WORK flag

When one the generic syscall entry code, use the syscall_work field in struct thread_info and specific SYSCALL_WORK flags to setup this syscall work. This flag has the advantage of being architecture independent. Users of the flag outside of the generic entry code should rely on the accessor