|
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
| #
51369649 |
| 20-Nov-2017 |
Pedro F. Giffuni <[email protected]> |
sys: further adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 3-Clause license.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for
sys: further adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 3-Clause license.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
Special thanks to Wind River for providing access to "The Duke of Highlander" tool: an older (2014) run over FreeBSD tree was useful as a starting point.
show more ...
|
|
Revision tags: release/10.4.0, release/11.1.0 |
|
| #
fbbd9655 |
| 28-Feb-2017 |
Warner Losh <[email protected]> |
Renumber copyright clause 4
Renumber cluase 4 to 3, per what everybody else did when BSD granted them permission to remove clause 3. My insistance on keeping the same numbering for legal reasons is
Renumber copyright clause 4
Renumber cluase 4 to 3, per what everybody else did when BSD granted them permission to remove clause 3. My insistance on keeping the same numbering for legal reasons is too pedantic, so give up on that point.
Submitted by: Jan Schaumann <[email protected]> Pull Request: https://github.com/freebsd/freebsd/pull/96
show more ...
|
|
Revision tags: release/11.0.1, release/11.0.0, release/10.3.0 |
|
| #
2f2f522b |
| 28-Sep-2015 |
Andriy Gapon <[email protected]> |
save some bytes by using more concise SDT_PROBE<n> instead of SDT_PROBE
SDT_PROBE requires 5 parameters whereas SDT_PROBE<n> requires n parameters where n is typically smaller than 5.
Perhaps SDT_P
save some bytes by using more concise SDT_PROBE<n> instead of SDT_PROBE
SDT_PROBE requires 5 parameters whereas SDT_PROBE<n> requires n parameters where n is typically smaller than 5.
Perhaps SDT_PROBE should be made a private implementation detail.
MFC after: 20 days
show more ...
|
|
Revision tags: release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0 |
|
| #
d9fae5ab |
| 26-Nov-2013 |
Andriy Gapon <[email protected]> |
dtrace sdt: remove the ugly sname parameter of SDT_PROBE_DEFINE
In its stead use the Solaris / illumos approach of emulating '-' (dash) in probe names with '__' (two consecutive underscores).
Revie
dtrace sdt: remove the ugly sname parameter of SDT_PROBE_DEFINE
In its stead use the Solaris / illumos approach of emulating '-' (dash) in probe names with '__' (two consecutive underscores).
Reviewed by: markj MFC after: 3 weeks
show more ...
|
| #
54366c0b |
| 25-Nov-2013 |
Attilio Rao <[email protected]> |
- 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 debug in sfxge is broken and it was never really tested. As it was not including correctly opt_kdtrace.h before it was never enabled so it was kept broken for a while. Fix this by using a protection stub, leaving sfxge driver authors the responsibility for fixing it appropriately [1].
Sponsored by: EMC / Isilon storage division Discussed with: rstone [0] Reported by: rstone [1] Discussed with: philip
show more ...
|
|
Revision tags: release/9.2.0, release/8.4.0 |
|
| #
593efaf9 |
| 21-Feb-2013 |
John Baldwin <[email protected]> |
Further refine the handling of stop signals in the NFS client. The changes in r246417 were incomplete as they did not add explicit calls to sigdeferstop() around all the places that previously passe
Further refine the handling of stop signals in the NFS client. The changes in r246417 were incomplete as they did not add explicit calls to sigdeferstop() around all the places that previously passed SBDRY to _sleep(). In addition, nfs_getcacheblk() could trigger a write RPC from getblk() resulting in sigdeferstop() recursing. Rather than manually deferring stop signals in specific places, change the VFS_*() and VOP_*() methods to defer stop signals for filesystems which request this behavior via a new VFCF_SBDRY flag. Note that this has to be a VFC flag rather than a MNTK flag so that it works properly with VFS_MOUNT() when the mount is not yet fully constructed. For now, only the NFS clients are set this new flag in VFS_SET().
A few other related changes: - Add an assertion to ensure that TDF_SBDRY doesn't leak to userland. - When a lookup request uses VOP_READLINK() to follow a symlink, mark the request as being on behalf of the thread performing the lookup (cnp_thread) rather than using a NULL thread pointer. This causes NFS to properly handle signals during this VOP on an interruptible mount.
PR: kern/176179 Reported by: Russell Cattelan (sigdeferstop() recursion) Reviewed by: kib MFC after: 1 month
show more ...
|
| #
7fc3ae51 |
| 28-Dec-2012 |
Oleksandr Tymoshenko <[email protected]> |
Fix build on ARM (and probably other platforms)
|
| #
4c44811c |
| 19-Dec-2012 |
Jeff Roberson <[email protected]> |
- Add new machine parsable KTR macros for timing events. - Use this new format to automatically handle syscalls and VOPs. This changes the earlier format but is still human readable.
Sponsored
- Add new machine parsable KTR macros for timing events. - Use this new format to automatically handle syscalls and VOPs. This changes the earlier format but is still human readable.
Sponsored by: EMC / Isilon Storage Division
show more ...
|
|
Revision tags: release/9.1.0, release/8.3.0 |
|
| #
f62f6c88 |
| 21-Feb-2012 |
Mikolaj Golub <[email protected]> |
Make vnode_if.awk parse vnode operations with underscores, like VOP_FOO_BAR.
Reviewed by: kib MFC after: 1 week
|
|
Revision tags: release/7.4.0, release/8.2.0 |
|
| #
79856499 |
| 22-Aug-2010 |
Rui Paulo <[email protected]> |
Add an extra comment to the SDT probes definition. This allows us to get use '-' in probe names, matching the probe names in Solaris.[1]
Add userland SDT probes definitions to sys/sdt.h.
Sponsored
Add an extra comment to the SDT probes definition. This allows us to get use '-' in probe names, matching the probe names in Solaris.[1]
Add userland SDT probes definitions to sys/sdt.h.
Sponsored by: The FreeBSD Foundation Discussed with: rwaston [1]
show more ...
|
|
Revision tags: release/8.1.0, release/7.3.0, release/8.0.0, release/7.2.0 |
|
| #
ff8a07fd |
| 29-Mar-2009 |
Robert Watson <[email protected]> |
Add SDT DTrace probes for VFS vnode operations in the vfs:vop provider namespace. These are inserted dynamically into the VOP_..._AP() functions created from vnode_if.src. Each VOP has entry and re
Add SDT DTrace probes for VFS vnode operations in the vfs:vop provider namespace. These are inserted dynamically into the VOP_..._AP() functions created from vnode_if.src. Each VOP has entry and return probes, as arg0 the primary vnode, arg1 the vnode operation argument structure pointer, providing access to IN and OUT arguments, and for return probes, arg2 the return value.
MFC after: 1 month Sponsored by: Google, Inc.
show more ...
|
|
Revision tags: release/7.1.0, release/6.4.0 |
|
| #
c439bdd8 |
| 03-Nov-2008 |
John Baldwin <[email protected]> |
Remove some unused and broken code that attempted to not invoke locking asserts on NULL vnode pointers. All the vnode assertion routines already check for NULL vnode pointers.
|
|
Revision tags: release/7.0.0, release/6.3.0, release/6.2.0 |
|
| #
44d6e87b |
| 30-May-2006 |
Diomidis Spinellis <[email protected]> |
- Add two checks for syntax errors - Improve error reporting - Remove redundant conditionals
|
| #
f69ec7af |
| 30-May-2006 |
Diomidis Spinellis <[email protected]> |
Assertion code specifications are introduced using special character sequences that are distinct from comments. %% is used for argument locks; %! for pre- and post-conditions.
|
| #
3cd62520 |
| 26-May-2006 |
Diomidis Spinellis <[email protected]> |
Update usage comment to match reality.
|
|
Revision tags: release/5.5.0, release/6.1.0 |
|
| #
0430a5e2 |
| 14-Dec-2005 |
Dag-Erling Smørgrav <[email protected]> |
Eradicate caddr_t from the VFS API.
|
| #
e26b05cf |
| 14-Dec-2005 |
Dag-Erling Smørgrav <[email protected]> |
Nuke vnodeop_desc.vdesc_transports, which has been unused since the dawn of time (or the inception of ncvs, whichever came last)
|
|
Revision tags: release/6.0.0 |
|
| #
679985d0 |
| 09-Jun-2005 |
Suleiman Souhlal <[email protected]> |
Allow EVFILT_VNODE events to work on every filesystem type, not just UFS by: - Making the pre and post hooks for the VOP functions work even when DEBUG_VFS_LOCKS is not defined. - Moving the KNOTE ac
Allow EVFILT_VNODE events to work on every filesystem type, not just UFS by: - Making the pre and post hooks for the VOP functions work even when DEBUG_VFS_LOCKS is not defined. - Moving the KNOTE activations into the corresponding VOP hooks. - Creating a MNTK_NOKNOTE flag for the mnt_kern_flag field of struct mount that permits filesystems to disable the new behavior. - Creating a default VOP_KQFILTER function: vfs_kqfilter()
My benchmarks have not revealed any performance degradation.
Reviewed by: jeff, bde Approved by: rwatson, jmg (kqueue changes), grehan (mentor)
show more ...
|
|
Revision tags: release/5.4.0 |
|
| #
680a1ec6 |
| 11-Apr-2005 |
Jeff Roberson <[email protected]> |
- Add the character "E" to the understood lock types. This means the VOP requires an exclusive lock.
Sponsored by: Isilon Systems, Inc.
|
| #
119798b3 |
| 08-Feb-2005 |
Poul-Henning Kamp <[email protected]> |
Add VOP_FOO_APV() which takes a pointer to the vop_vector.
This allows stacked or partitioned filesystems to say "Continue the normal resolution from here", for instace from FFS to UFS.
Use VNASSER
Add VOP_FOO_APV() which takes a pointer to the vop_vector.
This allows stacked or partitioned filesystems to say "Continue the normal resolution from here", for instace from FFS to UFS.
Use VNASSERT() instead of KASSERT().
show more ...
|
|
Revision tags: release/4.11.0 |
|
| #
de8a6c06 |
| 13-Jan-2005 |
Poul-Henning Kamp <[email protected]> |
Get rid of the VDESC() macro while the pot is boiling anyway, it is only used from generate files now, so we might as well generate the right stuff from the start.
|
| #
63f89abf |
| 13-Jan-2005 |
Poul-Henning Kamp <[email protected]> |
Change the generated VOP_ macro implementations to improve type checking and KASSERT coverage.
After this check there is only one "nasty" cast in this code but there is a KASSERT to protect against
Change the generated VOP_ macro implementations to improve type checking and KASSERT coverage.
After this check there is only one "nasty" cast in this code but there is a KASSERT to protect against the wrong argument structure behind that cast.
Un-inlining the meat of VOP_FOO() saves 35kB of text segment on a typical kernel with no change in performance.
We also now run the checking and tracing on VOP's which have been layered by nullfs, umapfs, deadfs or unionfs.
Add new (non-inline) VOP_FOO_AP() functions which take a "struct foo_args" argument and does everything the VOP_FOO() macros used to do with checks and debugging code.
Add KASSERT to VOP_FOO_AP() check for argument type being correct.
Slim down VOP_FOO() inline functions to just stuff arguments into the struct foo_args and call VOP_FOO_AP().
Put function pointer to VOP_FOO_AP() into vop_foo_desc structure and make VCALL() use it instead of the current offsetoff() hack.
Retire vcall() which implemented the offsetoff()
Make deadfs and unionfs use VOP_FOO_AP() calls instead of VCALL(), we know which specific call we want already.
Remove unneeded arguments to VCALL() in nullfs and umapfs bypass functions.
Remove unused vdesc_offset and VOFFSET().
Generally improve style/readability of the generated code.
show more ...
|
| #
60727d8b |
| 07-Jan-2005 |
Warner Losh <[email protected]> |
/* -> /*- for license, minor formatting changes
|
| #
57c75b8f |
| 13-Dec-2004 |
Warner Losh <[email protected]> |
Rather than casting through a (void *) to avoid the aliasing warning, do things correctly from an aliasing perspective. Put the vop_generic_args element as the first element for all the vop_*_args a
Rather than casting through a (void *) to avoid the aliasing warning, do things correctly from an aliasing perspective. Put the vop_generic_args element as the first element for all the vop_*_args and adjust the code to take the address of that instead of the structure.
OK'd based on a vague description by: phk
show more ...
|
| #
98a67cd8 |
| 13-Dec-2004 |
Warner Losh <[email protected]> |
Cast from the specific vop_*_args to vop_generic_args via a (void *) pointer to eliminate the hundreds of warnings that we have in tree at the moment.
# Chances are good that all the struct vop_*_ar
Cast from the specific vop_*_args to vop_generic_args via a (void *) pointer to eliminate the hundreds of warnings that we have in tree at the moment.
# Chances are good that all the struct vop_*_args should have, as its # first element, the struct vop_generic_args, and when necessary to # reference it, we just take its address rather than going through # this double case.
show more ...
|