Revision tags: release/14.3.0 |
|
#
e9897199 |
| 03-Jun-2025 |
Konstantin Belousov <kib@FreeBSD.org> |
pseudofs: make dup name an error instead of panic
There are enough cases where the duplicate name is caused by dubious hardware configuration. Stopping the whole system instead of failing a driver,
pseudofs: make dup name an error instead of panic
There are enough cases where the duplicate name is caused by dubious hardware configuration. Stopping the whole system instead of failing a driver, or even a diagnostic subsystem in a driver, is more user-friendly.
Another issue right now is that the check is only present for the INVARIANTS builds, silently accepting the request to create an entry with the existing name on production builds.
Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D50669
show more ...
|
#
b63f298b |
| 04-Jun-2025 |
Konstantin Belousov <kib@FreeBSD.org> |
pseudofs: fix typo in comment
Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 3 days Differential revision: https://reviews.freebsd.org/D50669
|
#
9a139fac |
| 03-Jun-2025 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
pseudofs: enhance KASSERT with more information
Add the name and type information to a KASSERT for 'homonymous siblings'. Without this (or a core file) we do not even know which entry to look for.
pseudofs: enhance KASSERT with more information
Add the name and type information to a KASSERT for 'homonymous siblings'. Without this (or a core file) we do not even know which entry to look for. This should make reporting and debugging a tad more simple.
Prompted by: PR 287165
show more ...
|
Revision tags: release/13.4.0-p5, release/13.5.0-p1, release/14.2.0-p3, release/13.5.0, release/14.2.0-p2, release/14.1.0-p8, release/13.4.0-p4, release/14.1.0-p7, release/14.2.0-p1, release/13.4.0-p3, release/14.2.0, release/13.4.0, release/14.1.0, release/13.3.0, release/14.0.0 |
|
#
e738085b |
| 17-Aug-2023 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Remove my middle name.
|
#
685dc743 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line .c pattern
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
#
88a795e8 |
| 25-Apr-2023 |
Stefan Eßer <se@FreeBSD.org> |
sys/fs: do not report blocks allocated for synthetic file systems
The pseudo file systems (devfs, fdescfs, procfs, etc.) report total and available blocks and inodes despite being synthetic with no
sys/fs: do not report blocks allocated for synthetic file systems
The pseudo file systems (devfs, fdescfs, procfs, etc.) report total and available blocks and inodes despite being synthetic with no underlying storage device to which those values could be applied.
The current code of these file systems tends to report a fixed number of total blocks but no free blocks, and in the case of procfs, libprocfs, linsysfs also no free inodes.
This can be irritating in e.g. the "df" output, since 100% of the resources seem to be in use, but it can also create warnings in monitoring tools used for capacity management.
This patch makes these file systems return the same value for the total and free parameters, leading to 0% in use being displayed by "df". Since there is no resource that can be exhausted, this appears to be a sensible result.
Reviewed by: mckusick Differential Revision: https://reviews.freebsd.org/D39442
show more ...
|
Revision tags: release/13.2.0 |
|
#
7f723243 |
| 02-Apr-2023 |
Dmitry Chagin <dchagin@FreeBSD.org> |
pseudofs: Microoptimize struct pfs_node
Since 81167243b the size of struct pfs_node is 280 bytes, so the kernel memory allocator takes memory from 384 bytes sized bucket. However, the length of the
pseudofs: Microoptimize struct pfs_node
Since 81167243b the size of struct pfs_node is 280 bytes, so the kernel memory allocator takes memory from 384 bytes sized bucket. However, the length of the node name is mostly short, e.g., for Linux emulation layer it is up to 16 bytes. The size of struct pfs_node w/o pfs_name is 152 bytes, i.e., we have 104 bytes left to fit the node name into the 256 bytes-sized bucket.
Reviewed by: des Differential revision: https://reviews.freebsd.org/D39381 MFC after: 1 month
show more ...
|
Revision tags: release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0 |
|
#
75dfc66c |
| 27-Feb-2020 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r358269 through r358399.
|
#
d3d10ed2 |
| 24-Feb-2020 |
Pawel Biernacki <kaktus@FreeBSD.org> |
Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (10 of many)
r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly mark
Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (10 of many)
r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly marked). Use it in preparation for a general review of all nodes.
This is non-functional change that adds annotations to SYSCTL_NODE and SYSCTL_PROC nodes using one of the soon-to-be-required flags.
Approved by: kib (mentor, blanket) Differential Revision: https://reviews.freebsd.org/D23629
show more ...
|
Revision tags: release/12.1.0 |
|
#
48c426f2 |
| 13-Oct-2019 |
Mateusz Guzik <mjg@FreeBSD.org> |
pseudofs: use MNTK_NOMSYNC
Reviewed by: kib Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D22009
|
#
419f843f |
| 17-Sep-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r352319 through r352435.
|
#
cf389852 |
| 14-Sep-2019 |
Edward Tomasz Napierala <trasz@FreeBSD.org> |
Make pseudofs(9) create directory entries in order, instead of the reverse.
This fixes Linux sysctl(8) binary - it assumes the first two directory entries are always "." and "..". There might be oth
Make pseudofs(9) create directory entries in order, instead of the reverse.
This fixes Linux sysctl(8) binary - it assumes the first two directory entries are always "." and "..". There might be other Linux apps affected by this.
NB it might be a good idea to rewrite it using queue(3).
Reviewed by: kib MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D21550
show more ...
|
Revision tags: release/11.3.0 |
|
#
18b18078 |
| 25-Feb-2019 |
Enji Cooper <ngie@FreeBSD.org> |
MFhead@r344527
|
#
a8fe8db4 |
| 25-Feb-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r344178 through r344512.
|
#
81167243 |
| 20-Feb-2019 |
Matt Macy <mmacy@FreeBSD.org> |
PFS: Bump NAMELEN and don't require clients to be sleepable
- debugfs consumers expect to be able to export names more than 48 characters
- debugfs consumers expect to be able to hold locks across
PFS: Bump NAMELEN and don't require clients to be sleepable
- debugfs consumers expect to be able to export names more than 48 characters
- debugfs consumers expect to be able to hold locks across calls and are able to handle allocation failures
Reviewed by: hps@ MFC after: 1 week Sponsored by: iX Systems Differential Revision: https://reviews.freebsd.org/D19256
show more ...
|
Revision tags: release/12.0.0, release/11.2.0 |
|
#
d63027b6 |
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
sys/fs: further adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
sys/fs: further adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
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.
show more ...
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0 |
|
#
27067774 |
| 16-Aug-2016 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r303250 through r304235.
|
#
29ffb32c |
| 03-Aug-2016 |
Konstantin Belousov <kib@FreeBSD.org> |
Remove Giant asserts. Update comment.
Owning Giant in the init/uninit is accidental due to the moment where VFS modules initialization is performed, and is not enforced by the VFS interface. The G
Remove Giant asserts. Update comment.
Owning Giant in the init/uninit is accidental due to the moment where VFS modules initialization is performed, and is not enforced by the VFS interface. The Giant lock does not prevent a parallel execution of the code, it is VFS which implements the proper protocol.
Approved by: des (pseudofs maintainer) Sponsored by: The FreeBSD Foundation MFC after: 1 week
show more ...
|
#
6828ba63 |
| 03-Aug-2016 |
Konstantin Belousov <kib@FreeBSD.org> |
Some style changes. Fix a typo in comment.
Approved by: des (pseudofs maintainer) Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
Revision tags: release/10.3.0, release/10.2.0 |
|
#
416ba5c7 |
| 22-Jun-2015 |
Navdeep Parhar <np@FreeBSD.org> |
Catch up with HEAD (r280229-r284686).
|
#
37a48d40 |
| 28-May-2015 |
Glen Barber <gjb@FreeBSD.org> |
MFH: r282615-r283655
Sponsored by: The FreeBSD Foundation
|
#
63cc3320 |
| 24-May-2015 |
Dmitry Chagin <dchagin@FreeBSD.org> |
Hide vfs.pfs.trace variable if it is not used.
|
Revision tags: release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0 |
|
#
cfe30d02 |
| 19-Jun-2013 |
Gleb Smirnoff <glebius@FreeBSD.org> |
Merge fresh head.
|
Revision tags: release/8.4.0 |
|
#
d9a44755 |
| 08-Feb-2013 |
David E. O'Brien <obrien@FreeBSD.org> |
Sync with HEAD.
|
Revision tags: release/9.1.0 |
|
#
300675f6 |
| 27-Nov-2012 |
Alexander Motin <mav@FreeBSD.org> |
MFC
|