Re: Current status of seccomp support in the m68k kernel?

[Michael Schmitz <schmitzmic@gmail.com>]

Hi Adrian,

see:

https://lore.kernel.org/r/20220127074158.25888-1-schmitzmic@gmail.com

for the last version of this patch series.

According to 
https://lore.kernel.org/r/CAMuHMdVUFt2BX7m4BAMP8aJ9Si=sj8eupPf_oQ4_THPH5+b6HQ@mail.gmail.com, 
Geert had taken the first patch for v5.19, and it's showing up as commit 
ee9a94d93adcc147052da15816580b007d3b0a5b.

Hmmm... patch #3 does no longer cleanly apply since 
tracehook_report_syscall_entry() was replaced by 
ptrace_report_syscall_entry(). I'd better sent an updated version.

I have a further patch that adds m68k support to the kernel seccomp 
self-test code that may need updating to current mainline, will add that 
to the series.

Cheers,

	Michael

Am 10.01.2023 um 01:37 schrieb John Paul Adrian Glaubitz:
> Hi!
>
> I have finally found some time again to work on the userland m68k
> support for
> seccomp and I was wondering what the current state of the kernel support
> is?
>
> If I remember correctly there were some patches posted that needed testing?
>
> Adrian
>