src/sys/fs/devfs, branch releng/13.4 FreeBSD source tree devfs_allocv(): style 2024-05-19T00:59:13+00:00 Konstantin Belousov kib@FreeBSD.org 2024-05-07T12:33:01+00:00 7c23465541f328acab2192c870be31324ce436d9 (cherry picked from commit 6d79564fe341c8dbf09405cae1a0a76460aaf8aa) 
(cherry picked from commit 6d79564fe341c8dbf09405cae1a0a76460aaf8aa)
Fix MNT_IGNORE for devfs, fdescfs and nullfs 2024-04-27T14:58:39+00:00 Doug Rabson dfr@FreeBSD.org 2023-08-26T09:32:32+00:00 1d06b45463bf404b5010f2370cb39b68a32da323 The MNT_IGNORE flag can be used to mark certain filesystem mounts so that utilities such as df(1) and mount(8) can filter out those mounts by default. This can be used, for instance, to reduce the noise from running container workloads inside jails which often have at least three and sometimes as many as ten mounts per container. The flag is supplied by the nmount(2) system call and is recorded so that it can be reported by statfs(2). Unfortunately several filesystems override the default behaviour and mask out the flag, defeating its purpose. This change preserves the MNT_IGNORE flag for those filesystems so that it can be reported correctly. MFC after: 1 week (cherry picked from commit b5c4616582cebdcf4dee909a3c2f5b113c4ae59e) 
The MNT_IGNORE flag can be used to mark certain filesystem mounts so
that utilities such as df(1) and mount(8) can filter out those mounts by
default. This can be used, for instance, to reduce the noise from
running container workloads inside jails which often have at least three
and sometimes as many as ten mounts per container.

The flag is supplied by the nmount(2) system call and is recorded so
that it can be reported by statfs(2). Unfortunately several filesystems
override the default behaviour and mask out the flag, defeating its
purpose. This change preserves the MNT_IGNORE flag for those filesystems
so that it can be reported correctly.

MFC after:	1 week

(cherry picked from commit b5c4616582cebdcf4dee909a3c2f5b113c4ae59e)
cdevpriv(9): add iterator 2024-03-30T08:32:23+00:00 Konstantin Belousov kib@FreeBSD.org 2024-03-22T02:58:00+00:00 8d9ed1dd5088901a0000c30b6a5ee6a38beb491d (cherry picked from commit d3efbe0132b24e8660df836905cda7662f85a154) 
(cherry picked from commit d3efbe0132b24e8660df836905cda7662f85a154)
kcmp(2): implement for devfs files 2024-02-11T01:40:29+00:00 Konstantin Belousov kib@FreeBSD.org 2024-01-19T21:36:50+00:00 890d1f392a1ed6792f0f1563f601181e5b9935a7 (cherry picked from commit 5c41d888de1aba0e82531fb6df4cc3b6989d37bd) 
(cherry picked from commit 5c41d888de1aba0e82531fb6df4cc3b6989d37bd)
devfs(5): Fix a typo in a source code comment 2024-01-23T06:45:52+00:00 Gordon Bergling gbe@FreeBSD.org 2024-01-20T16:25:45+00:00 a17275e29f89d2ceb197787095eb93042631a55b - s/interpeted/interpreted/ (cherry picked from commit 7cf293536ebacc92150be12e0be928500e670610) 
- s/interpeted/interpreted/

(cherry picked from commit 7cf293536ebacc92150be12e0be928500e670610)
devfs: add integrity asserts for cdevp_list 2023-09-28T01:29:52+00:00 Jason A. Harmening jah@FreeBSD.org 2023-09-19T13:44:34+00:00 ee596061e5a5952f1ddc68627492fbe94af8344b It's possible for misuse of cdev KPIs or for bugs in devfs itself to result in e.g. a cdev object's container being freed while still on the global list used to populate each devfs mount; see PR 273418 for a recent example. Since a node may be marked inactive well before it is reaped from the list, add a new flag solely to track list membership, and employ it in some basic list integrity assertions to catch bad actors. Discussed with: kib, mjg (cherry picked from commit 67864268da53b792836f13be10299de8cd62997e) 
It's possible for misuse of cdev KPIs or for bugs in devfs itself to
result in e.g. a cdev object's container being freed while still on the
global list used to populate each devfs mount; see PR 273418 for a
recent example.

Since a node may be marked inactive well before it is reaped from the
list, add a new flag solely to track list membership, and employ it in
some basic list integrity assertions to catch bad actors.

Discussed with:	kib, mjg

(cherry picked from commit 67864268da53b792836f13be10299de8cd62997e)
sys: Remove $FreeBSD$: two-line .h pattern 2023-08-23T17:43:20+00:00 Warner Losh imp@FreeBSD.org 2023-08-22T01:31:02+00:00 f8167e0404dab9ffeaca95853dd237ab7c587f82 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ Similar commit in current: (cherry picked from commit 95ee2897e98f) 
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/

Similar commit in current:
(cherry picked from commit 95ee2897e98f)
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD 2023-07-25T15:13:49+00:00 Warner Losh imp@FreeBSD.org 2023-05-10T15:40:58+00:00 caa41f641755c935b036e17440a3b49329c904ed The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause. Discussed with: pfg MFC After: 3 days Sponsored by: Netflix (cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b) 
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.

Discussed with:		pfg
MFC After:		3 days
Sponsored by:		Netflix

(cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b)
sys/fs: do not report blocks allocated for synthetic file systems 2023-05-01T08:11:44+00:00 Stefan Eßer se@FreeBSD.org 2023-04-25T07:40:05+00:00 3270f21597fb35f7cdbc39f0f09eaf4f84e79fe6 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 (cherry picked from commit 88a795e80c03ff1d960d830ee273589664ab06cc) 
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

(cherry picked from commit 88a795e80c03ff1d960d830ee273589664ab06cc)
fs: fix a few common typos in source code comments 2022-02-09T06:18:56+00:00 Gordon Bergling gbe@FreeBSD.org 2022-02-06T12:48:31+00:00 061c19c2bd29454eba63d33526fde8f5b5274477 - s/quadradically/quadratically/ - s/persistant/persistent/ Obtained from: NetBSD (cherry picked from commit 8ea3ceda7644b7b93532d0c31b50ac5fa61e51a3) 
- s/quadradically/quadratically/
- s/persistant/persistent/

Obtained from:	NetBSD

(cherry picked from commit 8ea3ceda7644b7b93532d0c31b50ac5fa61e51a3)