![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / src / sys / kern
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: MAIN
Revision 1.92 / (download) - annotate - [select for diffs], Mon Aug 9 20:49:10 2021 UTC (2 years, 8 months ago) by andvar
Branch: MAIN
CVS Tags: thorpej-ifq-base,
thorpej-ifq,
thorpej-altq-separation-base,
thorpej-altq-separation,
netbsd-10-base,
netbsd-10-0-RELEASE,
netbsd-10-0-RC6,
netbsd-10-0-RC5,
netbsd-10-0-RC4,
netbsd-10-0-RC3,
netbsd-10-0-RC2,
netbsd-10-0-RC1,
netbsd-10,
bouyer-sunxi-drm-base,
bouyer-sunxi-drm,
HEAD
Changes since 1.91: +3 -3
lines
Diff to previous 1.91 (colored)
fix various typos in compatibility, mainly in comments.
Revision 1.91 / (download) - annotate - [select for diffs], Wed Nov 4 19:27:41 2020 UTC (3 years, 5 months ago) by pgoyette
Branch: MAIN
CVS Tags: thorpej-i2c-spi-conf2-base,
thorpej-i2c-spi-conf2,
thorpej-i2c-spi-conf-base,
thorpej-i2c-spi-conf,
thorpej-futex2-base,
thorpej-futex2,
thorpej-futex-base,
thorpej-cfargs2-base,
thorpej-cfargs2,
thorpej-cfargs-base,
thorpej-cfargs,
cjep_sun2x-base1,
cjep_sun2x-base,
cjep_sun2x,
cjep_staticlib_x-base1,
cjep_staticlib_x-base,
cjep_staticlib_x
Changes since 1.90: +22 -36
lines
Diff to previous 1.90 (colored)
Merge the two separate sets of init/fini routines and unbreak the build. XXX Still does not fix the problems noted with 32-bit arm - that will need a lot more thought.
Revision 1.90 / (download) - annotate - [select for diffs], Wed Nov 4 18:12:18 2020 UTC (3 years, 5 months ago) by pgoyette
Branch: MAIN
Changes since 1.89: +4 -4
lines
Diff to previous 1.89 (colored)
Finish the proper naming of the module init/fini routines. Should fix the "ptrace cannot be used by unpriv user" issue reported by Rin Okuyama (thanks for the detailed report and analysis).
Revision 1.89 / (download) - annotate - [select for diffs], Sun Nov 1 18:51:02 2020 UTC (3 years, 5 months ago) by pgoyette
Branch: MAIN
Changes since 1.88: +2 -4
lines
Diff to previous 1.88 (colored)
Separate the compat_netbsd32_coredump from the compat_netbsd32 and coredump modules, into its own module. Welcome to 7.99.75 !!!
Revision 1.88 / (download) - annotate - [select for diffs], Sun Oct 25 15:55:36 2020 UTC (3 years, 5 months ago) by pgoyette
Branch: MAIN
Branch point for: thorpej-futex
Changes since 1.87: +18 -4
lines
Diff to previous 1.87 (colored)
ptrace_Common is a module unto itself. Don't use the ptrace module's init/fini routines.
Revision 1.87 / (download) - annotate - [select for diffs], Tue Oct 20 20:28:55 2020 UTC (3 years, 5 months ago) by christos
Branch: MAIN
Changes since 1.86: +2 -214
lines
Diff to previous 1.86 (colored)
Basic register read/write functionality and lwp setting are always provided by the kernel because they are needed by multiple things (ptrace/procfs/coredump), so move them to sys_process_lwpstatus (this file should be renamed to sys_process_common.c?)
Revision 1.86 / (download) - annotate - [select for diffs], Mon Oct 19 14:52:19 2020 UTC (3 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.85: +23 -1
lines
Diff to previous 1.85 (colored)
Rollback unintended changes in the previous commit
Revision 1.85 / (download) - annotate - [select for diffs], Mon Oct 19 14:47:01 2020 UTC (3 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.84: +2 -35
lines
Diff to previous 1.84 (colored)
Remove obsolete references to 4.4BSD papers
Revision 1.84 / (download) - annotate - [select for diffs], Thu Oct 15 17:37:36 2020 UTC (3 years, 6 months ago) by mgorny
Branch: MAIN
Changes since 1.83: +4 -4
lines
Diff to previous 1.83 (colored)
Fix the machine-dependent ptrace requests to respect LWP number Fix the machine-dependent ptrace register-related requests (e.g. PT_GETXMMREGS, PT_GETXSTATE on x86) to correctly respect the LWP number passed as the data argument. Before this change, these requests did not operate on the requested LWP of a multithreaded program. This change required moving ptrace_update_lwp() out of unit scope, and changing ptrace_machdep_dorequest() function to take a pointer to pointer as the second argument, consistently with ptrace_regs(). I am planning to extend the ATF ptrace() register tests in the future to check for regressions in multithreaded programs, as time permits. Reviewed by kamil.
Revision 1.83 / (download) - annotate - [select for diffs], Sat May 30 08:41:22 2020 UTC (3 years, 10 months ago) by maxv
Branch: MAIN
Changes since 1.82: +7 -3
lines
Diff to previous 1.82 (colored)
Introduce PTRACE_REGS_ALIGN, and on x86, enforce a 16-byte alignment, due to fpregs having fxsave which requires 16-byte alignment. Reported-by: syzbot+f44d47e617ebf7fda081@syzkaller.appspotmail.com
Revision 1.82 / (download) - annotate - [select for diffs], Tue May 26 23:08:56 2020 UTC (3 years, 10 months ago) by kamil
Branch: MAIN
Changes since 1.81: +8 -11
lines
Diff to previous 1.81 (colored)
Avoid taking lwp_lock when calling process_sstep() for sibling LWPs This makes the code consistend between single-threaded and multi-threaded code.
Revision 1.81 / (download) - annotate - [select for diffs], Sat May 23 23:42:43 2020 UTC (3 years, 10 months ago) by ad
Branch: MAIN
Changes since 1.80: +6 -6
lines
Diff to previous 1.80 (colored)
Move proc_lock into the data segment. It was dynamically allocated because at the time we had mutex_obj_alloc() but not __cacheline_aligned.
Revision 1.80 / (download) - annotate - [select for diffs], Thu May 14 13:32:15 2020 UTC (3 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.79: +58 -2
lines
Diff to previous 1.79 (colored)
Introduce new ptrace(2) operations: PT_SET_SIGPASS and PT_GET_SIGPASS They deliver the logic of bypassing selected signals directly to the debuggee, without informing the debugger. This can be used to implement the QPassSignals GDB/LLDB protocol. This call can be useful to avoid signal races in ATF ptrace tests.
Revision 1.79 / (download) - annotate - [select for diffs], Fri May 8 10:35:51 2020 UTC (3 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.78: +4 -3
lines
Diff to previous 1.78 (colored)
Clear PSL_TRACEDCHILD on ptrace(PT_DETACH) This avoids potential race of detaching and attaching to a prestarted process and receiving SIGTRAP instead of SIGSTOP.
Revision 1.78 / (download) - annotate - [select for diffs], Sat Feb 22 09:24:05 2020 UTC (4 years, 1 month ago) by maxv
Branch: MAIN
CVS Tags: phil-wifi-20200421,
phil-wifi-20200411,
phil-wifi-20200406,
is-mlppp-base,
is-mlppp,
bouyer-xenpvh-base2,
bouyer-xenpvh-base1,
bouyer-xenpvh-base,
bouyer-xenpvh,
ad-namecache-base3
Changes since 1.77: +3 -3
lines
Diff to previous 1.77 (colored)
pass the address of the field, instead of relying on it being the first field of the structure, no functional change, ok kamil
Revision 1.77 / (download) - annotate - [select for diffs], Fri Jan 3 00:37:29 2020 UTC (4 years, 3 months ago) by kamil
Branch: MAIN
CVS Tags: ad-namecache-base2,
ad-namecache-base1,
ad-namecache-base
Branch point for: ad-namecache
Changes since 1.76: +6 -5
lines
Diff to previous 1.76 (colored)
Correct the rule to iterate over LWPs with PT_LWPNEXT and PT_LWPINFO Correctly exclude dead/dying/zombie and system threads. Fixes kern/54802 (gdb -p kills the kernel) by <martin>
Revision 1.76 / (download) - annotate - [select for diffs], Thu Dec 26 08:52:38 2019 UTC (4 years, 3 months ago) by kamil
Branch: MAIN
Changes since 1.75: +2 -34
lines
Diff to previous 1.75 (colored)
Put ptrace_read_lwpstatus() and process_read_lwpstatus() to a new file Fixes "no PTRACE" kernel build, in particular zaurus kernel=INSTALL_C700.
Revision 1.75 / (download) - annotate - [select for diffs], Wed Dec 25 15:54:02 2019 UTC (4 years, 3 months ago) by kamil
Branch: MAIN
Changes since 1.74: +3 -3
lines
Diff to previous 1.74 (colored)
Cast PTRACE_LWP_GETPRIVATE to (void *) through (intptr_t) Fixes sparc build.
Revision 1.74 / (download) - annotate - [select for diffs], Tue Dec 24 14:50:59 2019 UTC (4 years, 3 months ago) by kamil
Branch: MAIN
Changes since 1.73: +112 -2
lines
Diff to previous 1.73 (colored)
Introduce PT_LWPSTATUS + PT_LWPNEXT, obsolete PT_LWPINFO PT_LWPINFO is a legacy ptrace(2) operation that was originally intended to retrieve the thread (LWP) information inside a traced process. It has a number of flaws and is confused with PT_LWPINFO from FreeBSD. PT_LWPSTATUS and PT_LWPNEXT address the problems (shortly by: rename, removal of pl_event) and introduces new features: signal context (pl_sigpend, pl_sigmask), LWP name (pl_name), LWP TLS base address (pl_private). The private pointer was so far missing information for a debugger. PT_LWPSTATUS@nnn is now shipped with core(5) files and contain LWP specific information, so far missed in the core(5) files. PT_LWPSTATUS retrieves LWP information for the prompted thread. PT_LWPNEXT retrieves LWP information for the next thread, borrowing the semantics from NetBSD specific PT_LWPINFO. PT_LWPINFO is namespaced with __LEGACY_PT_LWPINFO and still available for the foreseeable future, without plans of removing it. Add ATF tests for PT_LWPSTATUS + PT_LWPNEXT. Keep ATF tests for PT_LWPINFO. Switch GDB to new API. Proposed on tech-kern@.
Revision 1.73 / (download) - annotate - [select for diffs], Fri Nov 22 05:01:44 2019 UTC (4 years, 4 months ago) by rin
Branch: MAIN
Changes since 1.72: +9 -6
lines
Diff to previous 1.72 (colored)
Fix regression introduced to ptrace_regs() in rev 1.27: http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/kern/sys_ptrace_common.c#rev1.27 Size of registers should be determined from tracer, NOT tracee. Now, 64-bit tracer can manipulate registers of 32-bit tracee again. gdb for amd64 works for i386 binaries to some extent. XXX pullup to netbsd-9 and -8.
Revision 1.72 / (download) - annotate - [select for diffs], Sun Nov 17 02:22:14 2019 UTC (4 years, 5 months ago) by rin
Branch: MAIN
CVS Tags: phil-wifi-20191119
Changes since 1.71: +11 -3
lines
Diff to previous 1.71 (colored)
Fix pointer arithmetic for 32-bit process on LP64 kernel in process_auxv_offset(). Now, PIOD_READ_AUXV works fine with COMPAT_NETBSD32. XXX pullup to netbsd-9 and netbsd-8
Revision 1.71 / (download) - annotate - [select for diffs], Wed Nov 13 15:48:36 2019 UTC (4 years, 5 months ago) by pgoyette
Branch: MAIN
Changes since 1.70: +3 -3
lines
Diff to previous 1.70 (colored)
Return success if no coredump module is loaded/hooked.
Revision 1.70 / (download) - annotate - [select for diffs], Sun Nov 10 14:20:50 2019 UTC (4 years, 5 months ago) by pgoyette
Branch: MAIN
Changes since 1.69: +4 -3
lines
Diff to previous 1.69 (colored)
Convert the coredump_vec modular function pointer to use the new compat_hook mechanism. XXX Should be pulled up to -9 despite the kernel <--> module ABI XXX change.
Revision 1.69 / (download) - annotate - [select for diffs], Wed Oct 16 18:29:49 2019 UTC (4 years, 6 months ago) by christos
Branch: MAIN
Changes since 1.68: +6 -6
lines
Diff to previous 1.68 (colored)
Add and use __FPTRCAST, requested by uwe@
Revision 1.68 / (download) - annotate - [select for diffs], Wed Oct 16 15:27:38 2019 UTC (4 years, 6 months ago) by christos
Branch: MAIN
Changes since 1.67: +6 -6
lines
Diff to previous 1.67 (colored)
Add void * function pointer casts. There are different ways to "fix" those
warnings:
1. this one: add a void * cast (which I think is the least intrusive)
2. add pragmas to elide the warning
3. add intermediate inline conversion functions
4. change the called function prototypes, adding unused arguments and
converting some of the pointer arguments to void *.
5. make the functions varyadic (which defeats the purpose of checking)
6. pass command line flags to elide the warning
I did try 3 and 4 and I was not pleased with the result (sys_ptrace_common.c)
(3) added too much code and defines, and (4) made the regular use clumsy.
Revision 1.67 / (download) - annotate - [select for diffs], Sat Oct 12 12:04:37 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.66: +7 -3
lines
Diff to previous 1.66 (colored)
Avoid signed integer overflow for -lwp where lwp is INT_MIN Reported-by: syzbot+68b80b44b898e66da3fc@syzkaller.appspotmail.com
Revision 1.66 / (download) - annotate - [select for diffs], Wed Oct 9 13:19:43 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.65: +28 -20
lines
Diff to previous 1.65 (colored)
Introduce new ptrace(2) operation PT_STOP It works like: - kill(SIGSTOP) for unstopped tracee - ptrace(PT_CONTINUE,SIGSTOP) for stopped tracee The child will be stopped and always possible to be waited (with wait(2) like calls). For stopped traccee kill(SIGSTOP) has no effect. PT_CONTINUE+SIGSTOP cannot be used on an unstopped process (EBUSY). This operation is modeled after PT_KILL that is similar for the SIGKILL call. While there, allow PT_KILL on unstopped traced child. This operation is useful in an abnormal exit of a debugger from a signal handler, usually followed by waitpid(2) and ptrace(PT_DETACH).
Revision 1.65 / (download) - annotate - [select for diffs], Tue Oct 8 12:29:57 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.64: +3 -3
lines
Diff to previous 1.64 (colored)
Correct the same expression on both sides of | PR sw-bug/54610 by David Binderman
Revision 1.64 / (download) - annotate - [select for diffs], Mon Oct 7 21:32:51 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.63: +3 -3
lines
Diff to previous 1.63 (colored)
Fix typo in a comment
Revision 1.63 / (download) - annotate - [select for diffs], Thu Oct 3 23:11:11 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.62: +6 -2
lines
Diff to previous 1.62 (colored)
Add two KASSERTS in the ptrace(2) kernel code Verify that we will never return empty ptrace_state for CHILD/LWP event.
Revision 1.62 / (download) - annotate - [select for diffs], Thu Oct 3 22:48:44 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.61: +14 -8
lines
Diff to previous 1.61 (colored)
Separate flag for suspended by _lwp_suspend and suspended by a debugger Once a thread was stopped with ptrace(2), userland process must not be able to unstop it deliberately or by an accident. This was a Windows-style behavior that makes threading tracing fragile.
Revision 1.61 / (download) - annotate - [select for diffs], Tue Oct 1 21:49:50 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.60: +2 -7
lines
Diff to previous 1.60 (colored)
Remove 2 static asserts from the kernel ptrace code sizeof(pid) and sizeof(lwp) will unlikely ever change and the check can confuse. The assert has been moved to ATF t_ptrace_wait.c r.1.132. Requested by <christos>
Revision 1.60 / (download) - annotate - [select for diffs], Tue Oct 1 18:44:22 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.59: +15 -14
lines
Diff to previous 1.59 (colored)
Restore the old behavior in PT_GET_PROCESS_STATE For !child and !lwp events return zeroed struct ptrace_state. There is code that depends on it (GDB). Fixes PR toolchain/54590 by martin@
Revision 1.59 / (download) - annotate - [select for diffs], Mon Sep 30 21:13:33 2019 UTC (4 years, 6 months ago) by kamil
Branch: MAIN
Changes since 1.58: +19 -28
lines
Diff to previous 1.58 (colored)
Move TRAP_CHLD/TRAP_LWP ptrace information from struct proc to siginfo Storing struct ptrace_state information inside struct proc was vulnerable to synchronization bugs, as multiple events emitted in the same time were overwritting other ones. Cache the original parent process id in p_oppid. Reusing here p_opptr is in theory prone to slight race codition. Change the semantics of PT_GET_PROCESS_STATE, reutning EINVAL for calls prompting for the value in cases when there wasn't registered an appropriate event. Add an alternative approach to check the ptrace_state information, directly from the siginfo_t value returned from PT_GET_SIGINFO. The original PT_GET_PROCESS_STATE approach is kept for compat with older NetBSD and OpenBSD. New code is recommended to keep using PT_GET_PROCESS_STATE. Add a couple of compile-time asserts for assumptions in the code. No functional change intended in existing ptrace(2) software. All ATF ptrace(2) and ATF GDB tests pass. This change improves reliability of the threading ptrace(2) code.
Revision 1.58 / (download) - annotate - [select for diffs], Thu Jul 18 20:10:46 2019 UTC (4 years, 9 months ago) by kamil
Branch: MAIN
CVS Tags: netbsd-9-base
Branch point for: netbsd-9
Changes since 1.57: +5 -7
lines
Diff to previous 1.57 (colored)
Enhance locking of ptrace_update_lwp Replace lwp_delref() + mutex_enter() with: mutex_enter() + lwp_delref2(). This avoids extra taking and exiting from a mutex. Add missing mutex_exit() for LW_SYSTEM. Do not switch lwp for PT_SET_SIGINFO. This operation is not needed and avoids panic for >2 LWPs as p_lock is attempted to be entered again in a critical section.
Revision 1.57 / (download) - annotate - [select for diffs], Sat Jun 29 11:37:17 2019 UTC (4 years, 9 months ago) by maxv
Branch: MAIN
Changes since 1.56: +12 -5
lines
Diff to previous 1.56 (colored)
Fix bug, don't release the reflock if we didn't take it in the first place. Looks like there are other locking issues in here. Reported-by: syzbot+81d2c90809163ab1e13c@syzkaller.appspotmail.com
Revision 1.56 / (download) - annotate - [select for diffs], Mon Jun 24 20:29:41 2019 UTC (4 years, 9 months ago) by christos
Branch: MAIN
Changes since 1.55: +17 -5
lines
Diff to previous 1.55 (colored)
the tracer, not the tracee determine if we are going to convert the ptrace data from 64 to 32.
Revision 1.55 / (download) - annotate - [select for diffs], Tue Jun 11 23:18:55 2019 UTC (4 years, 10 months ago) by kamil
Branch: MAIN
Changes since 1.54: +14 -2
lines
Diff to previous 1.54 (colored)
Add support for PTRACE_POSIX_SPAWN to report posix_spawn(3) events posix_spawn(3) is a first class syscall in NetBSD, different to (V)FORK+EXEC as these operations are executed in one go. This differs to Linux and FreeBSD, where posix_spawn(3) is implemented with existing kernel primitives (clone(2), vfork(2), exec(3)) inside libc. Typically LLDB and GDB software is aware of FORK/VFORK events. As discussed with the LLDB community, instead of slicing the posix_spawn(3) operation into phases emulating (V)FORK+EXEC(+VFORK_DONE) and returning intermediate state to the debugger, that might have abnormal state, introduce new event type: PTRACE_POSIX_SPAWN. A debugger implementor can easily map it into existing fork+exec semantics or treat as a distinct event. There is no functional change for existing debuggers as there was no support for reporting posix_spawn(3) events on the kernel side.
Revision 1.54 / (download) - annotate - [select for diffs], Sat May 25 03:20:43 2019 UTC (4 years, 10 months ago) by kamil
Branch: MAIN
CVS Tags: phil-wifi-20190609
Changes since 1.53: +25 -22
lines
Diff to previous 1.53 (colored)
Relax prohibition of Program Counter set to 0x0 in ptrace(2) In PT_CONTINUE, PT_SYSCALL and PT_DETACH the 3rd argument of ptrace(2) allows to set PC. It used to be allowed to set PC to 0x0 without restrictions, later prohibited unconditionally. Change the condition and make it depending on vm.user_va0_disable. Whenever the VA 0 mapping is disallowed, reject setting PC to 0x0. While there comment truncated and empty transfers in PT_READ/PT_WRITE and PT_IO.
Revision 1.53 / (download) - annotate - [select for diffs], Fri May 10 21:08:26 2019 UTC (4 years, 11 months ago) by mgorny
Branch: MAIN
Changes since 1.52: +3 -3
lines
Diff to previous 1.52 (colored)
Fix typo: PT_GETFOREGS -> PT_GETFPREGS (NFC)
Revision 1.52 / (download) - annotate - [select for diffs], Thu May 2 00:23:01 2019 UTC (4 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.51: +6 -2
lines
Diff to previous 1.51 (colored)
Allow cancelled byte transfer in ptrace(2) again Current GDB depends on it on NetBSD (which is probably a GDB support bug). In future GDB will be examined for this and this code revisited.
Revision 1.51 / (download) - annotate - [select for diffs], Wed May 1 17:02:40 2019 UTC (4 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.50: +17 -2
lines
Diff to previous 1.50 (colored)
Disallow resuming program with PC=0x0 in ptrace(2) If the address parameter is 0, report error. It's a popular mistake to set Program Counter to 0x0. In certain kernels this is allowable parameter and causes portability issue. Disallow explicitly zeroed PC, instead of triggering a harder to debug crash later.
Revision 1.50 / (download) - annotate - [select for diffs], Tue Apr 30 22:32:01 2019 UTC (4 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.49: +6 -2
lines
Diff to previous 1.49 (colored)
Reject ptrace(2) PIOD_READ/WRITE operations with length 0 Return EINVAL for such invalid requests.
Revision 1.49 / (download) - annotate - [select for diffs], Tue Apr 30 20:50:30 2019 UTC (4 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.48: +10 -2
lines
Diff to previous 1.48 (colored)
Return EIO for empty memory transfer from ptrace(2) Certain operations of PT_READ/PT_WRITE and PIOD_READ/PIOD_WRITE can result in 0 byte transfer and the ptrace(2) call still returned success. GDB had a special handling of this case for PT_IO checking piod_len != 0, but in LLDB this corner case caused infinite loop and breakage. The LLDB case has been enhanced. Unfortunately the status of operation of PT_READ/PT_WRITE is not distinguishable between successful operation and empty opeartion. This renders this call into a questionable one. Change the behavior and return error with EIO in scenarios of truncated/empty byte transfers by PT_READ/PT_WRITE and empty byte transfers from PT_IO. No code changed is needed in GDB and LLDB.
Revision 1.48 / (download) - annotate - [select for diffs], Fri Apr 26 08:38:25 2019 UTC (4 years, 11 months ago) by pgoyette
Branch: MAIN
Changes since 1.47: +3 -3
lines
Diff to previous 1.47 (colored)
Set the "required modules" to NULL, not to an empty string. It really doesn't make that much difference to the code, but the output from modstat(8) is different! (With an empty string in the MODULE() macro modstat reports an empty string, but with a NULL in the macro, modstat prints a '-' just like it does for other "empty" fields.)
Revision 1.47 / (download) - annotate - [select for diffs], Sun Feb 3 03:19:28 2019 UTC (5 years, 2 months ago) by mrg
Branch: MAIN
CVS Tags: isaki-audio2-base,
isaki-audio2
Changes since 1.46: +4 -2
lines
Diff to previous 1.46 (colored)
- add or adjust /* FALLTHROUGH */ where appropriate - add __unreachable() after functions that can return but won't in this case, and thus can't be marked __dead easily
Revision 1.46 / (download) - annotate - [select for diffs], Thu Nov 29 11:45:52 2018 UTC (5 years, 4 months ago) by maxv
Branch: MAIN
CVS Tags: pgoyette-compat-20190127,
pgoyette-compat-20190118,
pgoyette-compat-1226
Changes since 1.45: +3 -2
lines
Diff to previous 1.45 (colored)
Fix stack info leak. + Possible info leak: [len=136, leaked=92] | #0 0xffffffff80baf397 in kleak_copyout | #1 0xffffffff80bd4155 in ptrace_copyout_siginfo | #2 0xffffffff80bd5348 in do_ptrace | #3 0xffffffff80bd40fe in sys_ptrace | #4 0xffffffff80259c42 in syscall
Revision 1.45 / (download) - annotate - [select for diffs], Sat Jun 23 03:32:48 2018 UTC (5 years, 9 months ago) by christos
Branch: MAIN
CVS Tags: phil-wifi-base,
pgoyette-compat-1126,
pgoyette-compat-1020,
pgoyette-compat-0930,
pgoyette-compat-0906,
pgoyette-compat-0728,
pgoyette-compat-0625
Branch point for: phil-wifi
Changes since 1.44: +29 -5
lines
Diff to previous 1.44 (colored)
Add some debugging in case someone else wants to debug gdb...
Revision 1.44 / (download) - annotate - [select for diffs], Wed May 30 23:54:03 2018 UTC (5 years, 10 months ago) by kamil
Branch: MAIN
Changes since 1.43: +3 -3
lines
Diff to previous 1.43 (colored)
Simplify comparison of two processes No need to check p_pid to compare whether two processes are the same. No functional change intended. Sponsored by <The NetBSD Foundation>
Revision 1.43 / (download) - annotate - [select for diffs], Tue May 29 23:34:18 2018 UTC (5 years, 10 months ago) by kamil
Branch: MAIN
Changes since 1.42: +10 -4
lines
Diff to previous 1.42 (colored)
Harden PT_ATTACH in ptrace(2) Don't allow to PT_ATTACH from a vfork(2)ed child (before exec(3)/_exit(3)) to its parent. Return error with EPERM errno. This scenario does not have a purpose and there is no clear picture how to route signals. Sponsored by <The NetBSD Foundation>
Revision 1.42 / (download) - annotate - [select for diffs], Sun May 20 04:00:35 2018 UTC (5 years, 11 months ago) by kamil
Branch: MAIN
CVS Tags: pgoyette-compat-0521
Changes since 1.41: +3 -3
lines
Diff to previous 1.41 (colored)
Make stopsigmask a non-static symbol now as it's used in ptrace(2) code This is a missing part of the previous commit. While there fix a typo in a newly added comment in the ptrace(2) code. Sponsored by <The NetBSD Foundation>
Revision 1.41 / (download) - annotate - [select for diffs], Sun May 20 03:51:31 2018 UTC (5 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.40: +12 -3
lines
Diff to previous 1.40 (colored)
Fix and enable traceme_signal_nohandler2 in ATF ptrace(2) tests traceme_signal_nohandler2 checks emitting SIGSTOP to a traced process with the PT_CONTINUE operation. The expected behavior is to simulate a behavior of receiving SIGSTOP, generating SIGCHLD to its parent (in this case the debugger) and ability to call wait(2)-like function receiving the stopped child event. The previous behavior was unstopping the process and it has been adjusted in the kernel code. FreeBSD keeps unstopping a process for emitting SIGSTOP. Linux handles this scenario in the same way as NetBSD now. While there, implement the missing bits in the userland ATF test for traceme_signal_nohandler2: receiving and validating 2nd SIGSTOP event and continuing the process, followed by its normal termination. Sponsored by <The NetBSD Foundation>
Revision 1.40 / (download) - annotate - [select for diffs], Tue May 1 16:37:23 2018 UTC (5 years, 11 months ago) by kamil
Branch: MAIN
CVS Tags: pgoyette-compat-0502
Changes since 1.39: +6 -7
lines
Diff to previous 1.39 (colored)
Implement PTRACE_VFORK Add support for tracing vfork(2) events in the context of ptrace(2). This API covers other frontends to fork1(9) like posix_spawn(2) or clone(2), if they cause parent to wait for exec(2) or exit(2) of the child. Changes: - Add new argument to sigswitch() determining whether we need to acquire the proc_lock or whether it's already held. - Refactor fork1(9) for fork(2) and vfork(2)-like events. Call sigswitch() from fork(1) for forking or vforking parent, instead of emitting kpsignal(9). We need to emit the signal and suspend the parent, returning to user and relock proc_lock. - Add missing prototype for proc_stop_done() in kern_sig.c. - Make sigswitch a public function accessible from other kernel code including <sys/signalvar.h>. - Remove an entry about unimplemented PTRACE_VFORK in the ptrace(2) man page. - Permin PTRACE_VFORK in the ptrace(2) frontend for userland. - Remove expected failure for unimplemented PTRACE_VFORK tests in the ATF ptrace(2) test-suite. - Relax signal routing constraints under a debugger for a vfork(2)ed child. This intended to protect from signaling a parent of a vfork(2)ed child that called PT_TRACE_ME, but wrongly misrouted other signals in vfork(2) use-cases. Add XXX comments about still existing problems and future enhancements: - correct vfork(2) + PT_TRACE_ME handling. - fork1(2) handling of scenarios when a process is collected in valid but rare cases. All ATF ptrace(2) fork[1-8] and vfork[1-8] tests pass. Fix PR kern/51630 by Kamil Rytarowski (myself). Sponsored by <The NetBSD Foundation>
Revision 1.39 / (download) - annotate - [select for diffs], Tue May 1 14:09:53 2018 UTC (5 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.38: +18 -6
lines
Diff to previous 1.38 (colored)
Add additional hardening in PT_TRACE_ME and PT_ATTACH Prohibit: - calling PT_TRACE_ME by initproc (PID1), - calling PT_ATTACH by initproc (PID1). PID1 and its parent cannot become a tracer. Sponsored by <The NetBSD Foundation>
Revision 1.38 / (download) - annotate - [select for diffs], Sun Apr 29 04:28:09 2018 UTC (5 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.37: +16 -4
lines
Diff to previous 1.37 (colored)
Harden the NetBSD PT_TRACE_ME operation
You can't say to the parent of a process to start tracing if:
(1) the parent is initproc,
(2) the child is already traced.
Rationale:
(1) - It has a side effect of being an anti-debugger functionality,
as we cannot kill initproc (PID1) and reset the traced flag.
- initproc is not a debugger, raising debugging events from a child
to initproc can result in at least a stopped/hanging process
in the system.
(2) - It does not make sense to be simultanously traced by two debuggers.
- It does not make sense to be traced twice by the same debugger.
Permit enable tracing for a parent that has been chroot(8)ed, as this is
harmless and the parent is already monitoring for child signals.
The same semantics exist in FreeBSD.
If you are looking for an antidebugging trick for old NetBSD (pre 8.0)
or other popular kernels, here is an example:
$ cat antidebug.c
#include <sys/types.h>
#include <sys/ptrace.h>
#include <stdlib.h>
#include <unistd.h>
#include <stdio.h>
#include <errno.h>
int
main(int argc, char **argv)
{
pid_t child;
int rv;
int n = 0;
child = fork();
if (child == 0) {
while (getppid() != 1)
continue;
rv = ptrace(PT_TRACE_ME, 0, 0, 0);
if (rv != 0)
abort();
printf("Try to detach to me with a debugger!! ");
printf("haha My PID is %d\n", getpid());
while (1) {
printf("%d\n", n++);
sleep(1);
}
}
exit(0);
}
A developer is no longer able to attach GDB, strace or LLDB to this program
without killing the initproc (your favourite system daemon).. this action
would be fatal for the operation of the whole Operating System stability.
Examples from a current non-NetBSD popular kernel:
$ ps -o ppid= -p 17904
1
$ strace -p 17904
strace: attach: ptrace(PTRACE_SEIZE, 17904): Operation not permitted
$ gdb -p 17904
[...]
Attaching to process 17904
warning: process 17904 is already traced by process 1
ptrace: Operation not permitted.
(gdb)
$ lldb-3.9 -p 17904
(lldb) process attach --pid 17904
error: attach failed: unable to attach
On NetBSD 8.0 and newer it is now guaranteed to have an option to kill
a malevolent (fake?) debugger and attach with a new tracer to the process.
Sponsored by <The NetBSD Foundation>
Revision 1.37 / (download) - annotate - [select for diffs], Fri Apr 27 16:50:56 2018 UTC (5 years, 11 months ago) by kamil
Branch: MAIN
Changes since 1.36: +13 -4
lines
Diff to previous 1.36 (colored)
Correct XXX comment in the ptrace(2) kernel code Explain I and D read/write operations and its history, removing dummy XXX comments. Sponsored by <The NetBSD Foundation>
Revision 1.36 / (download) - annotate - [select for diffs], Sun Apr 8 14:46:32 2018 UTC (6 years ago) by kamil
Branch: MAIN
CVS Tags: pgoyette-compat-0422,
pgoyette-compat-0415
Changes since 1.35: +12 -3
lines
Diff to previous 1.35 (colored)
Add new sysctl(3) entry: security.models.extensions.user_set_dbregs Model this new sysctl(3) entry after "user_set_cpu_affinity" in the same level of sysctl(3) switches. Allow to read unconditionally Debug Registers (no change here). This is convenient as even if a user of a debugger does not use hardware assisted watchpoints/breakpoints, a debugger can still prompt these values to store in an internal cache with context of registers. Reading them should have no security concerns. Add a paranoid MI switch that prohibits by default setting these registers by a regular user (non-superuser). Make this switch disabled by default. There are enough reserved bits out there to allow using them unconditionally on hardened hosts. Features shipped with Debug Registers are optional features in debuggers. There is no reduction in elementary functionality. Reviewed by <christos> Sponsored by <The NetBSD Foundation>
Revision 1.35 / (download) - annotate - [select for diffs], Mon Mar 5 11:24:34 2018 UTC (6 years, 1 month ago) by kamil
Branch: MAIN
CVS Tags: pgoyette-compat-base,
pgoyette-compat-0407,
pgoyette-compat-0330,
pgoyette-compat-0322,
pgoyette-compat-0315
Branch point for: pgoyette-compat
Changes since 1.34: +2 -29
lines
Diff to previous 1.34 (colored)
Remove PT_GET_SIGMASK / PT_SET_SIGMASK These operations cloned Linux's specific PTRACE_GETSIGMASK / PTRACE_SETSIGMASK. This feature was useful in applications like rr/criu/reptyr-like, where the ptrace(2) interface is abused for the purpose of constructing an arbitrary process. It's not reliable and not portable. For the NetBSD case it will be better to invent something dedicated for serializing and deserializing a process with threads. Noted on tech-toolchain@ and blog entry "LLDB restoration and return to ptrace(2)" https://blog.netbsd.org/tnf/entry/lldb_restoration_and_return_to
Revision 1.34 / (download) - annotate - [select for diffs], Mon Jan 8 06:10:30 2018 UTC (6 years, 3 months ago) by christos
Branch: MAIN
Changes since 1.33: +4 -4
lines
Diff to previous 1.33 (colored)
Use the proper process (the tracee) to get information about lwps and registers and the tracer for vmspace.
Revision 1.33 / (download) - annotate - [select for diffs], Mon Jan 8 04:45:53 2018 UTC (6 years, 3 months ago) by christos
Branch: MAIN
Changes since 1.32: +3 -3
lines
Diff to previous 1.32 (colored)
don't ignore error from copyout_piod
Revision 1.32 / (download) - annotate - [select for diffs], Thu Dec 28 18:29:45 2017 UTC (6 years, 3 months ago) by christos
Branch: MAIN
Changes since 1.31: +30 -24
lines
Diff to previous 1.31 (colored)
provide separate read and write functions to accomodate register functions that need a size argument.
Revision 1.31 / (download) - annotate - [select for diffs], Sat Dec 23 22:12:19 2017 UTC (6 years, 3 months ago) by christos
Branch: MAIN
Changes since 1.30: +19 -34
lines
Diff to previous 1.30 (colored)
Merge the code back; the problem was that since we are reading/writing
to a kernel address for PT_{READ,WRITE}_{I,D} we need the kernel vmspace.
Revision 1.30 / (download) - annotate - [select for diffs], Fri Dec 22 15:02:57 2017 UTC (6 years, 3 months ago) by kamil
Branch: MAIN
Changes since 1.29: +25 -9
lines
Diff to previous 1.29 (colored)
ptrace: Partially undo PT_{READ,WRITE}_{I,D} and unbreak these commands
The refactored code did not work and was generating EFAULT.
Sponsored by <The NetBSD Foundation>
Revision 1.29 / (download) - annotate - [select for diffs], Sun Dec 17 20:59:27 2017 UTC (6 years, 4 months ago) by christos
Branch: MAIN
Changes since 1.28: +12 -19
lines
Diff to previous 1.28 (colored)
handle siginfo requests for ptrace32
Revision 1.28 / (download) - annotate - [select for diffs], Sun Dec 17 15:43:27 2017 UTC (6 years, 4 months ago) by christos
Branch: MAIN
Changes since 1.27: +269 -276
lines
Diff to previous 1.27 (colored)
- reduce ifdef ugliness by moving it up top.
- factor out PT_IO and make PT_{READ,WRITE}_{I,D} use it
- factor out PT_DUMPCORE
- factor out sendsig code
... more to come ...
Revision 1.27 / (download) - annotate - [select for diffs], Sun Dec 17 04:35:21 2017 UTC (6 years, 4 months ago) by christos
Branch: MAIN
Changes since 1.26: +486 -471
lines
Diff to previous 1.26 (colored)
untangle the mess: - factor out common code - break each ptrace subcall to its own sub-function ... more to come ...
Revision 1.26 / (download) - annotate - [select for diffs], Sat Dec 9 05:18:45 2017 UTC (6 years, 4 months ago) by christos
Branch: MAIN
Changes since 1.25: +5 -5
lines
Diff to previous 1.25 (colored)
use process_*reg32 instead of struct *reg32.
Revision 1.25 / (download) - annotate - [select for diffs], Fri Dec 8 15:54:40 2017 UTC (6 years, 4 months ago) by christos
Branch: MAIN
Changes since 1.24: +7 -2
lines
Diff to previous 1.24 (colored)
add disgusting magic to handle compat_netbsd32 as a module.
Revision 1.24 / (download) - annotate - [select for diffs], Thu Dec 7 15:21:34 2017 UTC (6 years, 4 months ago) by christos
Branch: MAIN
Changes since 1.23: +77 -65
lines
Diff to previous 1.23 (colored)
Make {s,g}et{db,fp,}regs work again for PK_32 processes
XXX: pullup-8
Revision 1.23 / (download) - annotate - [select for diffs], Mon Aug 28 00:46:07 2017 UTC (6 years, 7 months ago) by kamil
Branch: MAIN
CVS Tags: tls-maxphys-base-20171202
Branch point for: tls-maxphys
Changes since 1.22: +5 -15
lines
Diff to previous 1.22 (colored)
Remove the filesystem tracing feature This is a legacy interface from 4.4BSD, and it was introduced to overcome shortcomings of ptrace(2) at that time, which are no longer relevant (performance). Today /proc/#/ctl offers a narrow subset of ptrace(2) commands and is not applicable for modern applications use beyond simplistic tracing scenarios. This removal will simplify kernel internals. Users will still be able to use all the other /proc files. This change won't affect other procfs files neither Linux compat features within mount_procfs(8). /proc/#/ctl isn't available on Linux. Remove: - /proc/#/ctl from mount_procfs(8) - P_FSTRACE note from the documentation of ps(1) - /proc/#/ctl and filesystem tracing documentation from mount_procfs(8) - KAUTH_REQ_PROCESS_PROCFS_CTL documentation from kauth(9) - source code file miscfs/procfs/procfs_ctl.c - PFSctl and procfs_doctl() from sys/miscfs/procfs/procfs.h - KAUTH_REQ_PROCESS_PROCFS_CTL from sys/sys/kauth.h - PSL_FSTRACE (0x00010000) from sys/sys/proc.h - P_FSTRACE (0x00010000) from sys/sys/sysctl.h Reduce code complexity after removal of this functionality. Update TODO.ptrace accordingly: remove two entries about /proc tracing. Do not keep legacy notes as comments in the headers about removed PSL_FSTRACE / P_FSTRACE, as this interface had little number of users (close or equal to zero). Proposed on tech-kern@. All filesystem tracing utility users are encouraged to switch to ptrace(2). Sponsored by <The NetBSD Foundation>
Revision 1.22 / (download) - annotate - [select for diffs], Wed May 3 15:53:31 2017 UTC (6 years, 11 months ago) by kamil
Branch: MAIN
CVS Tags: prg-localcount2-base3,
prg-localcount2-base2,
perseant-stdc-iso10646-base,
perseant-stdc-iso10646,
nick-nhusb-base-20170825,
netbsd-8-base,
matt-nb8-mediatek-base,
matt-nb8-mediatek
Branch point for: netbsd-8
Changes since 1.21: +2 -4
lines
Diff to previous 1.21 (colored)
Fix kernel panic triggered with LLDB PT_SETSTEP and PT_CLEARSTEP in the current design must unlock proc_lock and t->p_lock. These functions use lwp_delref() for a tracee with more than one LWP. This function internally lock (t->)p_lock and this is lock against self. There are coming new ATF test with PT_*STEP with multiple LWPs to catch these bugs in future changes. Sponsored by <The NetBSD Foundation>
Revision 1.21 / (download) - annotate - [select for diffs], Sat Apr 8 00:25:50 2017 UTC (7 years ago) by kamil
Branch: MAIN
CVS Tags: prg-localcount2-base1,
prg-localcount2-base,
pgoyette-localcount-20170426,
jdolecek-ncq-base,
jdolecek-ncq,
bouyer-socketcan-base1
Branch point for: prg-localcount2
Changes since 1.20: +51 -4
lines
Diff to previous 1.20 (colored)
Add new ptrace(2) API: PT_SETSTEP & PT_CLEARSTEP These operations allow to mark thread as a single-stepping one. This allows to i.a.: - single step and emit a signal (PT_SETSTEP & PT_CONTINUE) - single step and trace syscall entry and exit (PT_SETSTEP & PT_SYSCALL) The former is useful for debuggers like GDB or LLDB. The latter can be used to singlestep a usermode kernel. These examples don't limit use-cases of this interface. Define PT_*STEP only for platforms defining PT_STEP. Add new ATF tests setstep[1234]. These ptrace(2) operations first appeared in FreeBSD. Sponsored by <The NetBSD Foundation>
Revision 1.20 / (download) - annotate - [select for diffs], Wed Mar 29 22:48:03 2017 UTC (7 years ago) by kamil
Branch: MAIN
Changes since 1.19: +3 -4
lines
Diff to previous 1.19 (colored)
Revert previous. Pointed out by Christous Zoulas that ELF_AUX_ENTRIES * sizeof(AuxInfo) assumption is incomplete. There is emulation code that can use different values (smaller and larger).
Revision 1.19 / (download) - annotate - [select for diffs], Wed Mar 29 19:52:30 2017 UTC (7 years ago) by kamil
Branch: MAIN
Changes since 1.18: +4 -3
lines
Diff to previous 1.18 (colored)
Generate ELF AUXV for core(5) and ptrace(2) limited to the vector TYPE x V
Previously PT_DUMPCORE and PIOD_READ_AUXV and regular core dumping retrieved
the vector of AuxInfo {a_type, a_v} + MAXPATHLEN + ALIGN(1).
The extra data is not actually needed in the returned chunk. It can be
retrieved with PT_READ_I operations and it's the preferred way to access
them as the AuxInfo fields contain pointers (void* format) to them.
This changes the behavior of the kernel, no stable releases are affected
with this move. Current software is not affected as other systems already
stop generating data on AT_NULL. This streamlines the NetBSD behavior with
other ELF format OSes. This move also simplifies determination if we got
all the needed data inside the debugger and we no longer need to eliminate
the unneeded chunk at the end.
Sponsored by <The NetBSD Foundation>
Revision 1.18 / (download) - annotate - [select for diffs], Thu Feb 23 04:48:36 2017 UTC (7 years, 1 month ago) by kamil
Branch: MAIN
CVS Tags: pgoyette-localcount-20170320
Changes since 1.17: +2 -4
lines
Diff to previous 1.17 (colored)
Fix build of ports without PT_STEP Fallout after PT_*DBREGS introduction. Sponsored by <The NetBSD Foundation>
Revision 1.17 / (download) - annotate - [select for diffs], Thu Feb 23 03:34:22 2017 UTC (7 years, 1 month ago) by kamil
Branch: MAIN
Changes since 1.16: +86 -81
lines
Diff to previous 1.16 (colored)
Introduce PT_GETDBREGS and PT_SETDBREGS in ptrace(2) on i386 and amd64
This interface is modeled after FreeBSD API with the usage.
This replaced previous watchpoint API. The previous one was introduced
recently in NetBSD-current and remove its spurs without any
backward-compatibility.
Design choices for Debug Register accessors:
- exec() (TRAP_EXEC event) must remove debug registers from LWP
- debug registers are only per-LWP, not per-process globally
- debug registers must not be inherited after (v)forking a process
- debug registers must not be inherited after forking a thread
- a debugger is responsible to set global watchpoints/breakpoints with the
debug registers, to achieve this PTRACE_LWP_CREATE/PTRACE_LWP_EXIT event
monitoring function is designed to be used
- debug register traps must generate SIGTRAP with si_code TRAP_DBREG
- debugger is responsible to retrieve debug register state to distinguish
the exact debug register trap (DR6 is Status Register on x86)
- kernel must not remove debug register traps after triggering a trap event
a debugger is responsible to detach this trap with appropriate PT_SETDBREGS
call (DR7 is Control Register on x86)
- debug registers must not be exposed in mcontext
- userland must not be allowed to set a trap on the kernel
Implementation notes on i386 and amd64:
- the initial state of debug register is retrieved on boot and this value is
stored in a local copy (initdbregs), this value is used to initialize dbreg
context after PT_GETDBREGS
- struct dbregs is stored in pcb as a pointer and by default not initialized
- reserved registers (DR4-DR5, DR9-DR15) are ignored
Further ideas:
- restrict this interface with securelevel
Tested on real hardware i386 (Intel Pentium IV) and amd64 (Intel i7).
This commit enables 390 debug register ATF tests in kernel/arch/x86.
All tests are passing.
This commit does not cover netbsd32 compat code. Currently other interface
PT_GET_SIGINFO/PT_SET_SIGINFO is required in netbsd32 compat code in order to
validate reliably PT_GETDBREGS/PT_SETDBREGS.
This implementation does not cover FreeBSD specific defines in their
<x86/reg.h>: DBREG_DR7_LOCAL_ENABLE, DBREG_DR7_GLOBAL_ENABLE, DBREG_DR7_LEN_1
etc. These values tend to be reinvented by each tracer on its own. GNU
Debugger (GDB) works with NetBSD debug registers after adding this patch:
--- gdb/amd64bsd-nat.c.orig 2016-02-10 03:19:39.000000000 +0000
+++ gdb/amd64bsd-nat.c
@@ -167,6 +167,10 @@ amd64bsd_target (void)
#ifdef HAVE_PT_GETDBREGS
+#ifndef DBREG_DRX
+#define DBREG_DRX(d,x) ((d)->dr[(x)])
+#endif
+
static unsigned long
amd64bsd_dr_get (ptid_t ptid, int regnum)
{
Another reason to stop introducing unpopular defines covering machine
specific register macros is that these value varies across generations of
the same CPU family.
GDB demo:
(gdb) c
Continuing.
Watchpoint 2: traceme
Old value = 0
New value = 16
main (argc=1, argv=0x7f7fff79fe30) at test.c:8
8 printf("traceme=%d\n", traceme);
(Currently the GDB interface is not reliable due to NetBSD support bugs)
Sponsored by <The NetBSD Foundation>
Revision 1.16 / (download) - annotate - [select for diffs], Thu Feb 23 00:50:09 2017 UTC (7 years, 1 month ago) by kamil
Branch: MAIN
Changes since 1.15: +6 -5
lines
Diff to previous 1.15 (colored)
Improve PT_SET_SIGMASK and PT_GET_SIGMASK API in ptrace(2) Use proper check for LW_SYSTEM, don't depend on PT_GETREGS/PT_SETREGS. Don't allow to mask SA_CANTMASK signals with PT_SET_SIGMASK (this covers SIGSTOP and SIGKILL). Add new ATF tests: - setsigmask5 Verify that sigmask cannot be set to SIGKILL - setsigmask6 Verify that sigmask cannot be set to SIGSTOP Sponsored by <The NetBSD Foundation>
Revision 1.15 / (download) - annotate - [select for diffs], Wed Feb 22 23:43:43 2017 UTC (7 years, 1 month ago) by kamil
Branch: MAIN
Changes since 1.14: +71 -5
lines
Diff to previous 1.14 (colored)
Introduce new ptrace(2) API to allow/prevent exection of LWP
Introduce new API for debuggers to allow/prevent execution of the specified
thread.
New ptrace(2) operations:
PT_RESUME Allow execution of a specified thread, change its state
from suspended to continued. The addr argument is unused.
The data argument specifies the LWP ID.
This call is equivalent to _lwp_continue(2) called by a
traced process. This call does not change the general
process state from stopped to continued.
PT_SUSPEND Prevent execution of a specified thread, change its state
from continued to suspended. The addr argument is unused.
The data argument specifies the requested LWP ID.
This call is equivalent to _lwp_suspend(2) called by a
traced process. This call does not change the general
process state from continued to stopped.
This interface is modeled after FreeBSD, however with NetBSD specific arguments
passed to ptrace(2) -- FreeBSD passes only thread id, NetBSD passes process and
thread id.
Extend PT_LWPINFO operation in ptrace(2) to report suspended threads. In the
ptrace_lwpinfo structure in pl_event next to PL_EVENT_NONE and PL_EVENT_SIGNAL
add new value PL_EVENT_SUSPENDED.
Add new errno(2) value EDEADLK that might be returned by ptrace(2). It prevents
dead-locking in a scenario of resuming a process or thread that is prevented
from execution. This fixes bug that old API was vulnerable to this scenario.
Kernel bump delayed till introduction of PT_GETDBREGS/PT_SETDBREGS soon.
Add new ATF tests:
- resume1
Verify that a thread can be suspended by a debugger and later
resumed by the debugger
- suspend1
Verify that a thread can be suspended by a debugger and later
resumed by a tracee
- suspend2
Verify that the while the only thread within a process is
suspended, the whole process cannot be unstopped
Sponsored by <The NetBSD Foundation>
Revision 1.14 / (download) - annotate - [select for diffs], Sun Feb 12 06:09:52 2017 UTC (7 years, 2 months ago) by kamil
Branch: MAIN
Changes since 1.13: +35 -2
lines
Diff to previous 1.13 (colored)
Introduce new interface in ptrace(2) - PT_GET_SIGMASK and PT_SET_SIGMASK
Add new interface to add ability to get/set signal mask of a tracee.
It has been inspired by Linux PTRACE_GETSIGMASK and PTRACE_SETSIGMASK, but
adapted for NetBSD API.
This interface is used for checkpointing software to set/restore context
of a process including signal mask like criu or just to track this property
in reverse-execution software like Record and Replay Framework (rr).
Add new ATF tests for this interface
====================================
getsigmask1:
Verify that plain PT_SET_SIGMASK can be called
getsigmask2:
Verify that PT_SET_SIGMASK reports correct mask from tracee
setsigmask1:
Verify that plain PT_SET_SIGMASK can be called with empty mask
setsigmask2:
Verify that sigmask is preserved between PT_GET_SIGMASK and
PT_SET_SIGMASK
setsigmask3:
Verify that sigmask is preserved between PT_GET_SIGMASK, process
resumed and PT_SET_SIGMASK
setsigmask4:
Verify that new sigmask is visible in tracee
Kernel ABI bump delayed as there are more interfaces to come in ptrace(2).
Sponsored by <The NetBSD Foundation>
Revision 1.13 / (download) - annotate - [select for diffs], Sat Feb 11 19:32:41 2017 UTC (7 years, 2 months ago) by kamil
Branch: MAIN
Changes since 1.12: +4 -4
lines
Diff to previous 1.12 (colored)
Be paranoid about PT_SET_SIGINFO and PT_GET_SIGINFO in ptrace(2) Currently a tracer is prohibited to read and write memory of a tracee. Prohibit reading and faking signal information. Sponsored by <The NetBSD Foundation>
Revision 1.12 / (download) - annotate - [select for diffs], Thu Jan 26 03:54:01 2017 UTC (7 years, 2 months ago) by christos
Branch: MAIN
CVS Tags: nick-nhusb-base-20170204
Changes since 1.11: +2 -4
lines
Diff to previous 1.11 (colored)
don't return early holding a lock!
Revision 1.11 / (download) - annotate - [select for diffs], Wed Jan 25 17:55:47 2017 UTC (7 years, 2 months ago) by christos
Branch: MAIN
Changes since 1.10: +3 -3
lines
Diff to previous 1.10 (colored)
PR/51916: Kamil Rytarowski: Don't multiply es_arglen with ptrsz since it is already in bytes and contains the maximum possible size: ELF_AUX_ENTRIES * sizeof(auxv) + MAXPATHLEN + ALIGN
Revision 1.10 / (download) - annotate - [select for diffs], Sat Jan 14 06:36:52 2017 UTC (7 years, 3 months ago) by kamil
Branch: MAIN
CVS Tags: bouyer-socketcan-base
Branch point for: bouyer-socketcan
Changes since 1.9: +22 -2
lines
Diff to previous 1.9 (colored)
Introduce PTRACE_LWP_{CREATE,EXIT} in ptrace(2) and TRAP_LWP in siginfo(5)
Add interface in ptrace(2) to track thread (LWP) events:
- birth,
- termination.
The purpose of this thread is to keep track of the current thread state in
a tracee and apply e.g. per-thread designed hardware assisted watchpoints.
This interface reuses the EVENT_MASK and PROCESS_STATE interface, and
shares it with PTRACE_FORK, PTRACE_VFORK and PTRACE_VFORK_DONE.
Change the following structure:
typedef struct ptrace_state {
int pe_report_event;
pid_t pe_other_pid;
} ptrace_state_t;
to
typedef struct ptrace_state {
int pe_report_event;
union {
pid_t _pe_other_pid;
lwpid_t _pe_lwp;
} _option;
} ptrace_state_t;
#define pe_other_pid _option._pe_other_pid
#define pe_lwp _option._pe_lwp
This keeps size of ptrace_state_t unchanged as both pid_t and lwpid_t are
defined as int32_t-like integer. This change does not break existing
prebuilt software and has minimal effect on necessity for source-code
changes. In summary, this change should be binary compatible and shouldn't
break build of existing software.
Introduce new siginfo(5) type for LWP events under the SIGTRAP signal:
TRAP_LWP. This change will help debuggers to distinguish exact source of
SIGTRAP.
Add two basic t_ptrace_wait* tests:
lwp_create1:
Verify that 1 LWP creation is intercepted by ptrace(2) with
EVENT_MASK set to PTRACE_LWP_CREATE
lwp_exit1:
Verify that 1 LWP creation is intercepted by ptrace(2) with
EVENT_MASK set to PTRACE_LWP_EXIT
All tests are passing.
Surfing the previous kernel ABI bump to 7.99.59 for PTRACE_VFORK{,_DONE}.
Sponsored by <The NetBSD Foundation>
Revision 1.9 / (download) - annotate - [select for diffs], Fri Jan 13 23:00:35 2017 UTC (7 years, 3 months ago) by kamil
Branch: MAIN
Changes since 1.8: +29 -2
lines
Diff to previous 1.8 (colored)
Add support for PTRACE_VFORK_DONE and stub for PTRACE_VFORK in ptrace(2) PTRACE_VFORK is supposed to be used to track vfork(2)-like events, when parent gives birth to new process child and stops till it exits or calls exec(). Currently PTRACE_VFORK is a stub. PTRACE_VFORK_DONE is notification to notify a debugger that a parent has resumed after vfork(2)-like action. PTRACE_VFORK_DONE throws SIGTRAP with TRAP_CHLD. Sponsored by <The NetBSD Foundation>
Revision 1.8 / (download) - annotate - [select for diffs], Fri Jan 6 22:53:17 2017 UTC (7 years, 3 months ago) by kamil
Branch: MAIN
CVS Tags: pgoyette-localcount-20170107
Changes since 1.7: +78 -3
lines
Diff to previous 1.7 (colored)
Introduce new ptrace(2) interface: PT_SET_SIGINFO and PT_GET_SIGINFO
This interface is designed to read signal information emited to tracee and
fake this signal with new value.
This functionality is required to distinguish types of events that occured
in the tracee and intercepted by a debugger.
These accessors introduce a new structure type ptrace_siginfo:
/*
* Signal Information structure
*/
typedef struct ptrace_siginfo {
siginfo_t psi_siginfo; /* signal information structure */
lwpid_t psi_lwpid; /* destination LWP of the signal
* value 0 means the whole process
* (route signal to all LWPs) */
} ptrace_siginfo_t;
Include <sys/siginfo.h> in <sys/ptrace.h> in order to not break existing
software due to unknown symbol siginfo_t.
This interface has been proposed to the tech-kern@ mailing list.
Sponsored by <The NetBSD Foundation>
Revision 1.7 / (download) - annotate - [select for diffs], Thu Dec 15 12:04:18 2016 UTC (7 years, 4 months ago) by kamil
Branch: MAIN
Changes since 1.6: +102 -3
lines
Diff to previous 1.6 (colored)
Add support for hardware assisted watchpoints/breakpoints API in ptrace(2)
Add new ptrace(2) calls:
- PT_COUNT_WATCHPOINTS - count the number of available hardware watchpoints
- PT_READ_WATCHPOINT - read struct ptrace_watchpoint from the kernel state
- PT_WRITE_WATCHPOINT - write new struct ptrace_watchpoint state, this
includes enabling and disabling watchpoints
The ptrace_watchpoint structure contains MI and MD parts:
typedef struct ptrace_watchpoint {
int pw_index; /* HW Watchpoint ID (count from 0) */
lwpid_t pw_lwpid; /* LWP described */
struct mdpw pw_md; /* MD fields */
} ptrace_watchpoint_t;
For example amd64 defines MD as follows:
struct mdpw {
void *md_address;
int md_condition;
int md_length;
};
These calls are protected with the __HAVE_PTRACE_WATCHPOINTS guard.
Tested on amd64, initial support added for i386 and XEN.
Sponsored by <The NetBSD Foundation>
Revision 1.6 / (download) - annotate - [select for diffs], Mon Dec 5 22:07:16 2016 UTC (7 years, 4 months ago) by christos
Branch: MAIN
Changes since 1.5: +10 -3
lines
Diff to previous 1.5 (colored)
set the signal flag when the signal was sent to every lwp, not to just an individual one.
Revision 1.5 / (download) - annotate - [select for diffs], Sat Nov 19 19:06:12 2016 UTC (7 years, 5 months ago) by christos
Branch: MAIN
CVS Tags: nick-nhusb-base-20161204
Branch point for: nick-nhusb
Changes since 1.4: +3 -2
lines
Diff to previous 1.4 (colored)
Add FALLTHROUGH commit
Revision 1.4 / (download) - annotate - [select for diffs], Sat Nov 12 20:03:17 2016 UTC (7 years, 5 months ago) by christos
Branch: MAIN
Changes since 1.3: +3 -3
lines
Diff to previous 1.3 (colored)
back to using SIGSTOP..
Revision 1.3 / (download) - annotate - [select for diffs], Fri Nov 11 17:10:04 2016 UTC (7 years, 5 months ago) by christos
Branch: MAIN
Changes since 1.2: +3 -3
lines
Diff to previous 1.2 (colored)
kern/51621: When attaching to a child send it a SIGTRAP not a SIGSTOP like Linux and FreeBSD do.
Revision 1.2 / (download) - annotate - [select for diffs], Fri Nov 4 18:14:04 2016 UTC (7 years, 5 months ago) by christos
Branch: MAIN
Changes since 1.1: +3 -21
lines
Diff to previous 1.1 (colored)
deduplicate the complex lock reparent dance.
Revision 1.1 / (download) - annotate - [select for diffs], Wed Nov 2 00:11:59 2016 UTC (7 years, 5 months ago) by pgoyette
Branch: MAIN
CVS Tags: pgoyette-localcount-20161104
Branch point for: pgoyette-localcount
* Split sys/kern/sys_process.c into three parts:
1 - ptrace(2) syscall for native emulation
2 - common ptrace(2) syscall code (shared with compat_netbsd32)
3 - support routines that are shared with PROCFS and/or KTRACE
* Add module glue for #1 and #2. Both modules will be built-in to the
kernel if "options PTRACE" is included in the config file (this is
the default, defined in sys/conf/std).
* Mark the ptrace(2) syscall as modular in syscalls.master (generated
files will be committed shortly).
* Conditionalize all remaining portions of PTRACE code on a new kernel
option PTRACE_HOOKS.
XXX Instead of PROCFS depending on 'options PTRACE', we should probably
just add a procfs attribute to the sys/kern/sys_process.c file's
entry in files.kern, and add PROCFS to the "#if defineds" for
process_domem(). It's really confusing to have two different ways
of requiring this file.