sys: Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
sys/modules: normalize .CURDIR-relative paths to SRCTOPThis simplifies make output/logicTested with: `cd sys/modules; make ALL_MODULES=` on amd64MFC after: 1 monthSponsored by: Dell EMC Isilon
- For kernel compiled only with KDTRACE_HOOKS and not any lock debugging option, unbreak the lock tracing release semantic by embedding calls to LOCKSTAT_PROFILE_RELEASE_LOCK() direclty in the in
- For kernel compiled only with KDTRACE_HOOKS and not any lock debugging option, unbreak the lock tracing release semantic by embedding calls to LOCKSTAT_PROFILE_RELEASE_LOCK() direclty in the inlined version of the releasing functions for mutex, rwlock and sxlock. Failing to do so skips the lockstat_probe_func invokation for unlocking.- As part of the LOCKSTAT support is inlined in mutex operation, for kernel compiled without lock debugging options, potentially every consumer must be compiled including opt_kdtrace.h. Fix this by moving KDTRACE_HOOKS into opt_global.h and remove the dependency by opt_kdtrace.h for all files, as now only KDTRACE_FRAMES is linked there and it is only used as a compile-time stub [0].[0] immediately shows some new bug as DTRACE-derived support for debugin sfxge is broken and it was never really tested. As it was notincluding correctly opt_kdtrace.h before it was never enabled so itwas kept broken for a while. Fix this by using a protection stub,leaving sfxge driver authors the responsibility for fixing itappropriately [1].Sponsored by: EMC / Isilon storage divisionDiscussed with: rstone[0] Reported by: rstone[1] Discussed with: philip
show more ...
Fix 'make depend'
MFp4: anchie_soc2009 branch:Add kernel side support for Secure Neighbor Discovery (SeND), RFC 3971.The implementation consists of a kernel module that gets packets fromthe nd6 code, sends them t
MFp4: anchie_soc2009 branch:Add kernel side support for Secure Neighbor Discovery (SeND), RFC 3971.The implementation consists of a kernel module that gets packets fromthe nd6 code, sends them to user space on a dedicated socket and reinjectsthem back for further processing.Hooks are used from nd6 code paths to divert relevant packets to thesend implementation for processing in user space. The hooks are onlytriggered if the send module is loaded. In case no user spaceapplication is connected to the send socket, processing continuesnormaly as if the module would not be loaded. Unloading the moduleis not possible at this time due to missing nd6 locking.The native SeND socket is similar to a raw IPv6 socket but with its own,internal pseudo-protocol.Approved by: bz (mentor)