Seems like so. The fix [0] mainly replaces memcpys added by a former commit [1], which seems to be the main difference between the FreeBSD and Apple variant of ping [2], but probably that's not the source of the bug. What smells in there is 'hlen = ip->ip_hl << 2'
[0] https://github.com/freebsd/freebsd-src/commit/46d7b45a267b3d...
[1] https://github.com/freebsd/freebsd-src/commit/d9cacf605e2ac0...
[2] https://opensource.apple.com/source/network_cmds/network_cmd...
In Remote execution bug in BSD pingfreebsd
freebsd-src
C2012–2026
freebsd / freebsd-src
freebsd-src
The FreeBSD src tree publish-only repository. Experimenting with 'simple' pull requests....
122Distinct people
189Mentions
1Explicit recommenders
9.5KGitHub stars
What to know before exploring
What it is
The FreeBSD src tree publish-only repository. Experimenting with 'simple' pull requests....
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
My favorite piece of man trivia is from the source of the tunefs BSD man page, which contains: .\" Take this out and a Unix Daemon will dog your steps from now until .\" the…
beej71 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- openbsd/src · linked in 7 of the same discussions
- coreutils/coreutils · linked in 3 of the same discussions
- torvalds/linux · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year189 dated mentions
Observed mentions: 2012-05-14 23:44:07 UTC to 2026-10-26 20:08:28 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 16 | 1 | 15 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 17 | 0 | 17 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 14 | 1 | 13 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 28 | 2 | 26 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 20 | 1 | 19 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 24 | 0 | 24 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 23 | 0 | 23 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 10 | 2 | 8 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 5 | 0 | 5 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
FreeBSD Source:
This is the top level of the FreeBSD source directory.
FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.
A large community has continually developed it for more than thirty years.
Its advanced networking, security, and storage features have made FreeBSD the platform of choice for many of the busiest web sites and most pervasive embedded networking and storage devices.
For copyright information, please see the file COPYRIGHT in this directory.
Additional copyright information also exists for some sources in this tree - please see the specific source directories for more information.
The Makefile in this directory supports a number of targets for building components (or all) of the FreeBSD source tree.
See build(7), config(8), FreeBSD handbook on building userland, and Handbook for kernels for more information, including setting make(1) variables.
For information on the CPU architectures and platforms supported by FreeBSD, see the FreeBSD
website's Platforms page.
For official FreeBSD bootable images, see the release page.
Source Roadmap:
Directory
Description
bin
System/user commands.
cddl
Source code for third-party software under the Common Development and Distribution License.
contrib
Source code for third-party software.
crypto
Source code for cryptographic libraries and commands (see crypto/README).
etc
Template files for /etc.
include
System include files.
kerberos5
Build system for Kerberos 5 (Heimdal).
krb5
Build system for Kerberos 5 (MIT).
lib
System libraries.
libexec
System commands intended to be executed by other commands or daemons.
packages
Base system packages.
release
Makefiles and scripts used for building releases and VM images.
rescue
Build system for statically linked /rescue commands.
sbin
System commands.
secure
Build system for cryptographic libraries and commands (excluding Kerberos).
share
Shared resources.
stand
Boot loader sources.
sys
Kernel sources (see sys/README.md).
targets
Support for experimental DIRDEPS_BUILD
tests
Tests which can be run by Kyua. See tests/README for additional information.
tools
Ancillary utilities and tests (not included in the build).
usr.bin
User commands.
usr.sbin
System administration commands.
For information on synchronizing your source tree with one or more of the FreeBSD Project's development branches, please see FreeBSD Handbook.
Read the full README on GitHubWhat Hacker News says
24 sourcesTypically you keep a list entry in the struct:
https://man7.org/linux/man-pages/man3/stailq.3.html#EXAMPLES
The same list entry can be moved between several lists
using the same type.
If the struct need to be in multiple lists in the same time
you can keep multiple list entries in the same struct:
https://github.com/freebsd/freebsd-src/blob/69413598d2660054...
In In defense of linked lists> When it comes to avoiding forks, the question is why do egrep, fgrep have to be shell scripts rather than interpret the invocation name (argv[0]) for switching behavior.
I don't know. I'd have taken the argv[0] approach personally. And it's the approach some other grep implementations have taken too (eg https://github.com/freebsd/freebsd-src/blob/main/usr.bin/gre...).
The argv[0] approach (to me) feels like a right kind of compromise.
In We are stuck with egrep and fgrep (unless you like beating people)On FreeBSD, it checks the first character of the program name and modifies behavior based on that. See
https://github.com/freebsd/freebsd-src/blob/main/usr.bin/gre...
In We are stuck with egrep and fgrep (unless you like beating people)Here are a few implementations that did not get the memo:
coreutils ls: https://git.savannah.gnu.org/cgit/coreutils.git/log/src/ls.c
freebsd ls: https://github.com/freebsd/freebsd-src/commits/927f8d8bbbed7...
busybox ls: https://git.busybox.net/busybox/log/coreutils/ls.c
openbsd ls: https://github.com/openbsd/src/commits/master/bin/ls/ls.c
The latter seems to be the most stable, yet has been updated two years ago, many years after its first introduction.
In Outdated vs. Complete: In defense of apps that don’t need updatesI quite like the FreeBSD src tree, as it comprises both the system kernel as well as the userland applications. The folders are organized similarly to the OS file system hierarchy, which I find helpful for navigating the source tree. I found it accessible to slowly learn how various parts of the OS work under the hood and compound my knowledge faster due to less context shifting, since it’s self-contained in one source tree.
https://github.com/freebsd/freebsd-src
In Ask HN: What's the best source code you've read?This has been a feature upstream in FreeBSD for roughly 6 years.
If there is a connection RST, then the data buffered in the kernel is released (either freed immediately, or put into the page cache, depending on SF_NOCACHE).
sendfile_iodone() is called for completion. If there is no error, it marks the mbufs on the socket buffer holding the pages that were recently brought in as ready, and pokes the TCP stack to send them. If there was an error, it calls TCP's pru_abort() function to tear down the connection and release what's sitting on the socket buffer. See https://github.com/freebsd/freebsd-src/blob/main/sys/kern/ke...
In Serving Netflix Video Traffic at 800Gb/s and Beyond [pdf]To be honest, this has much more to do with Randall Stewart's RACK TCP, and his team's obsession with improving our member's QoE. Ironically, this costs a lot of CPU as compared to normal TCP (since it is doing pacing, limiting TSO burst sizes, etc). https://github.com/freebsd/freebsd-src/blob/main/sys/netinet...
In Serving Netflix Video Traffic at 800Gb/s and Beyond [pdf]FreeBSD has a /dev/cuse device, and a libcuse reimplemented on top of it, but it uses a different protocol from Linux's CUSE. You can see the FreeBSD implementation at https://github.com/freebsd/freebsd-src/blob/release/13.1.0/s... -- note how cuse_server_read() and cuse_server_write() are stubs.
I am somewhat familiar with this because I wrote a FUSE/CUSE server library in Rust, and tried porting it to FreeBSD. The FUSE bits worked with only minor issues[0][1], but the CUSE bits were completely different so I had to turn off that part of the library for FreeBSD targets.
[0] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253411
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253500
In An io_uring-based user-space block driver> PC component manufacturers offer Linux drivers for their hardware, sometimes it's binary blobs, etc. but at least there's some effort there.
I'm gonna say that it's a "generic" driver, which is totally fine on desktops but almost always (except for Thinkpads and Linux-focused laptop manufacturers) has a nasty edge case (modified chips or chip firmware) that just makes it incompatible. This isn't exclusive to Linux by the way, even Windows suffers from this exact problem (usually audio, fingerprint and touchpad).
Edit: for example, this is the FreeBSD code for HDA sound device (it's messy): https://github.com/freebsd/freebsd-src/blob/main/sys/dev/sou...
In Linux 5.19I never heard about anyone using yes to generate large data files/streams. Does anyone actually uses yes in a way that its daily CPU usage will be bigger than a rounding error?
Also very simple FreeBSD implementation [1] is not too slow on my 10-years old notebook:
> time yes test_string | dd of=/dev/null bs=1M count=65536
...
2646329200 bytes transferred in 1.709196 secs (1548288918 bytes/sec)
0.023u 0.850s 0:01.71 50.8% 5+166k 0+0io 0pf+0w
Firefox probably have used more CPU time while I was composing this comment - thanks to JS (in other tabs, HN is a rare example of a site which doesn't abuse my CPU). FF is almost always on the 1st line in top.
If you'll check top/powertop and a typical desktop or a server you'll likely find better targets than 'yes' to reduce energy use.
[1] https://github.com/freebsd/freebsd-src/blob/main/u
Read the rest
One of the reasons that NFS was so popular is that Sun gave away the protocol implementation. It's really interesting to see the technology behind that though. The whole protocol (both versions 2 and 3) is defined in a single file.[0] You run that file through the rpcgen program which spits out some .c and .h files which you can just link into your program. Of course on the server side you actually need to implement the code to handle those procedures, but on the client side it's all there, ready to use.
[0] https://github.com/freebsd/freebsd-src/blob/main/include/rpc...
In NFS: The Early Years>Service managers should take care of things like figuring out where stdout and stderr logs are sent to, so you shouldn't have to do that stuff in your service scripts.
You don't have to. The fact that Linux had anachronisms like that wasn't because of shell scripts, it's an entirely orthogonal issue; a typical rc script in, say, FreeBSD, looks like this: https://github.com/freebsd/freebsd-src/blob/main/libexec/rc/.... It's declarative, it's easy to understand, but it also provides you with flexibility when you need it, as opposed to one-off hacks with custom, fixed functionality and random syntax.
In What FreeBSD can offer compared to other operating systems (2020)net80211: validate Mesh ID length in ieee80211_parse_beacon
https://github.com/freebsd/freebsd-src/commit/fb8c87b4f3bfdf...
In CVE-2022-23088 – FreeBSD Network Subsystem Remote Code Execution VulnerabilityIdentifying slow pieces of boot: https://github.com/freebsd/freebsd-src/search?q=TSENTER , etc: https://github.com/freebsd/freebsd-src/blob/main/sys/sys/tsl... , and then eliminating low hanging fruit (many, but not all of his recent commits): https://freshbsd.org/freebsd/src/branch/main?merge=false&aut...
In FreeBSD 13.1Showing the 15 most recent of 24 sources. Enable JavaScript to search and browse every indexed mention.