src/sys/netgraph/ng_parse.c, branch releng/13.4 FreeBSD source tree sys: Remove $FreeBSD$: one-line .h pattern 2023-08-23T17:43:22+00:00 Warner Losh imp@FreeBSD.org 2023-08-22T01:31:09+00:00 4b40a16f0d188422227478889b38cc341d50f88f Remove /^\s*\*+\s*\$FreeBSD\$.*$\n/ Similar commit in current: (cherry picked from commit 2ff63af9b88c) 
Remove /^\s*\*+\s*\$FreeBSD\$.*$\n/

Similar commit in current:
(cherry picked from commit 2ff63af9b88c)
ng_parse: IP address parsing in netgraph eating too many characters 2021-06-08T10:14:34+00:00 Markus Stoff markus@stoffdv.at 2021-05-18T20:35:33+00:00 f18b7f239dcd75a192891232bc1fc099805f7d76 Once the final component of the IP address has been parsed, the offset on the input must not be advanced, as this would remove an unparsed character from the input. Submitted by: Markus Stoff Reviewed by: donner Differential Revision: https://reviews.freebsd.org/D26489 (cherry picked from commit 63b6a08ce2467b8e230e7a4ecb3e1ddf1b48851c) 
Once the final component of the IP address has been parsed, the offset
on the input must not be advanced, as this would remove an unparsed
character from the input.

Submitted by:	Markus Stoff
Reviewed by:	donner
Differential Revision: https://reviews.freebsd.org/D26489

(cherry picked from commit 63b6a08ce2467b8e230e7a4ecb3e1ddf1b48851c)
net: clean up empty lines in .c and .h files 2020-09-01T21:19:14+00:00 Mateusz Guzik mjg@FreeBSD.org 2020-09-01T21:19:14+00:00 662c13053f4bf2d6245ba7e2b66c10d1cd5c1fb9 






Revert r327828, r327949, r327953, r328016-r328026, r328041:
2018-01-21T15:42:36+00:00

Pedro F. Giffuni
pfg@FreeBSD.org

2018-01-21T15:42:36+00:00

ac2fffa4b74cd83963f0d462c379c7f50eeabf20

Uses of mallocarray(9).

The use of mallocarray(9) has rocketed the required swap to build FreeBSD.
This is likely caused by the allocation size attributes which put extra pressure
on the compiler.

Given that most of these checks are superfluous we have to choose better
where to use mallocarray(9). We still have more uses of mallocarray(9) but
hopefully this is enough to bring swap usage to a reasonable level.

Reported by:	wosch
PR:		225197





Uses of mallocarray(9).

The use of mallocarray(9) has rocketed the required swap to build FreeBSD.
This is likely caused by the allocation size attributes which put extra pressure
on the compiler.

Given that most of these checks are superfluous we have to choose better
where to use mallocarray(9). We still have more uses of mallocarray(9) but
hopefully this is enough to bring swap usage to a reasonable level.

Reported by:	wosch
PR:		225197







netgraph: make some use of mallocarray(9).
2018-01-15T21:19:21+00:00

Pedro F. Giffuni
pfg@FreeBSD.org

2018-01-15T21:19:21+00:00

3b0a4e40a08c8c3d0f6862648b3ac0126d2d15e4

Focus on code where we are doing multiplications within malloc(9). None of
these ire likely to overflow, however the change is still useful as some
static checkers can benefit from the allocation attributes we use for
mallocarray.

This initial sweep only covers malloc(9) calls with M_NOWAIT. No good
reason but I started doing the changes before r327796 and at that time it
was convenient to make sure the sorrounding code could handle NULL values.

X-Differential revision: https://reviews.freebsd.org/D13837





Focus on code where we are doing multiplications within malloc(9). None of
these ire likely to overflow, however the change is still useful as some
static checkers can benefit from the allocation attributes we use for
mallocarray.

This initial sweep only covers malloc(9) calls with M_NOWAIT. No good
reason but I started doing the changes before r327796 and at that time it
was convenient to make sure the sorrounding code could handle NULL values.

X-Differential revision: https://reviews.freebsd.org/D13837







Fix a bunch of -Wcast-qual warnings in netgraph's ng_parse.c, by using
2015-01-30T21:59:53+00:00

Dimitry Andric
dim@FreeBSD.org

2015-01-30T21:59:53+00:00

1bb25a82ab860aa71821b3f3e78661525637eec0

__DECONST.  No functional change.

MFC after:	3 days





__DECONST.  No functional change.

MFC after:	3 days







Fix compilation warning.
2013-02-15T07:58:51+00:00

Gleb Smirnoff
glebius@FreeBSD.org

2013-02-15T07:58:51+00:00

dc9b4fcacb1d7c7252064caca283c845fbaa4661

Sponsored by:	Nginx, Inc





Sponsored by:	Nginx, Inc







Mark MALLOC_DEFINEs static that have no corresponding MALLOC_DECLAREs.
2011-11-07T06:44:47+00:00

Ed Schouten
ed@FreeBSD.org

2011-11-07T06:44:47+00:00

d745c852becf3792a2185003947324721209195a

This means that their use is restricted to a single C file.





This means that their use is restricted to a single C file.







remove RESTARTABLE_PANICS option
2011-07-25T09:12:48+00:00

Andriy Gapon
avg@FreeBSD.org

2011-07-25T09:12:48+00:00

7a0b13ed28443e669cf479791ad96cce3d95e17c

This is done per request/suggestion from John Baldwin
who introduced the option.  Trying to resume normal
system operation after a panic is very unpredictable
and dangerous.  It will become even more dangerous
when we allow a thread in panic(9) to penetrate all
lock contexts.
I understand that the only purpose of this option was
for testing scenarios potentially resulting in panic.

Suggested by:	jhb
Reviewed by:	attilio, jhb
X-MFC-After:	never
Approved by:	re (kib)





This is done per request/suggestion from John Baldwin
who introduced the option.  Trying to resume normal
system operation after a panic is very unpredictable
and dangerous.  It will become even more dangerous
when we allow a thread in panic(9) to penetrate all
lock contexts.
I understand that the only purpose of this option was
for testing scenarios potentially resulting in panic.

Suggested by:	jhb
Reviewed by:	attilio, jhb
X-MFC-After:	never
Approved by:	re (kib)







Retire the MALLOC and FREE macros.  They are an abomination unto style(9).
2008-10-23T15:53:51+00:00

Dag-Erling Smørgrav
des@FreeBSD.org

2008-10-23T15:53:51+00:00

1ede983cc905643549d8cae56a9d0e28fc68375f

MFC after:	3 months





MFC after:	3 months