Re: [PATCH v10 0/3] Add kernel seccomp support for m68k

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Eric,

Am 04.05.2022 um 09:53 schrieb Eric W. Biederman:
Michael Schmitz <schmitzmic@xxxxxxxxx> writes:

Patch 3 adds the test for TIF_SECCOMP thread info flag to call
into syscall_trace_enter() when seccomp syscall filtering
is active, which was missing from earlier versions (classic
MMU m68k only - need some help with the test for 68000 and
coldfire).

The previous version required the TIF_SYSCALL_TRACE
flag to be set for syscall filtering to work

The rest of the series remains unchanged from v9.

Tested on ARAnyM, 63 out of 89 seccomp_bpf tests now pass
(33 with the old version).

I hope you didn't waste too much effort on testing v8/v9, Adrian.
Should have a suitably large brown paper bag somewhere yet :-(

Has any progress been made on testing or merging this patch series?

This series totally dropped off my radar, sorry. I had run out of options to test, and have been too busy to do much about that.

I was just thinking it might be nice if the only callers of
ptrace_report_syscall were ptrace_report_syscall_entry and
ptrace_report_syscall_exit.

Just merging patch 1 would be enough there AFAICS. Any reason not to do that, Geert?

Cheers,

	Michael




Eric




[Index of Archives]     [Video for Linux]     [Yosemite News]     [Linux S/390]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux