Hi Dmitry, On Mon, 3 Sep 2018 at 19:42, Dmitry V. Levin <ldv@xxxxxxxxxxxx> wrote: > > On Mon, Sep 03, 2018 at 01:26:15PM -0400, Joseph C. Sible wrote: > > Signed-off-by: Joseph C. Sible <josephcsible@xxxxxxxxx> > > --- > > man2/ptrace.2 | 23 ++++++++++++++++------- > > 1 file changed, 16 insertions(+), 7 deletions(-) > > > > diff --git a/man2/ptrace.2 b/man2/ptrace.2 > > index aea63d2..69699cc 100644 > > --- a/man2/ptrace.2 > > +++ b/man2/ptrace.2 > [...] > > @@ -735,6 +728,22 @@ argument is treated as for > > .RI ( addr > > is ignored.) > > .TP > > +.BR PTRACE_SET_SYSCALL " (since Linux 2.6.16)" > > +.\" commit 3f471126ee53feb5e9b210ea2f525ed3bb9b7a7f > > +When in syscall-enter-stop, change the number of the syscall about to > > +be executed to the number specified in the > > +.I data > > +argument. The > > +.I addr > > +argument is ignored. This request is currently > > +.\" As of 4.19-rc2 > > +supported only on arm (and arm64, though only for backwards compatibility), > > +.\" commit 27aa55c5e5123fa8b8ad0156559d34d7edff58ca > > +but most other architectures have other means of accomplishing this > > +(usually by changing the register that the userland code passed the > > +syscall number in). > > +.\" see change_syscall in tools/testing/selftests/seccomp/seccomp_bpf.c > > I suggest replacing the reference to that huge file with a reference to > syscall(2) manpage that contains more detailed information in a much more > readable form. I'm not too worried about this, since the reference is just a comment in the page source, but I doiid also include your suggestion of strace's linux/*/set_scno.c files in comment in the page source. Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
