Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

Linux 7.2-rc5 Fixing Longstanding Bug In IPv4 Networking Over Firewire

Дата публикации: 26-07-2026 10:38:22

Firewire still isn't dead yet on Linux. Current plans call for maintaining IEEE-1394 Firewire on Linux at least through 2029 and with today's Linux 7.2-rc5 kernel release is a fix for those wanting to leverage IPv4 networking over Firewire...

Основное содержимое страницы с новостью.

LINUX NETWORKING

Firewire still isn't dead yet on Linux. Current plans call for maintaining IEEE-1394 Firewire on Linux at least through 2029 and with today's Linux 7.2-rc5 kernel release is a fix for those wanting to leverage IPv4 networking over Firewire.

RFC 2734 is the nearly thirty year old standard for IPv4 datagrams over IEEE-1394 Firewire. Mainlined since 2009 for their modern (at the time) IEEE-1394 driver stack has been the "fw-ipv4" driver to provide this IPv4 support. But it turns out that since then there has been a notable bug in this driver.

Seventeen years after this IPv4 Firewire driver was upstreamed, it was realized the driver fails to properly reassemble a complete datagram if it's stored across multiple buffer ranges in the list. Open-source developer Ruoyu Wang realized this notable bug in the Firewire networking code that has existed the entire time of this IPv4 Firewire support. Explaining in the patch to fix it:

"Those neighbor lookups currently assume that the current fragment always has a real next or previous fragment. At a list edge, the next or previous entry is the list head, not a struct fwnet_fragment_info.

The gap checks also compare against the old edge of the current fragment instead of the edge after adding the new fragment. As a result, a fragment that bridges two existing ranges may leave two adjacent ranges unmerged, so fwnet_pd_is_complete() can miss a complete datagram.

Check for the list head before looking up the neighboring fragment, and compare the neighbor against the new fragment's far edge when deciding whether to merge all three ranges."

While Ruoyu Wang discovered this issue and patched this long-standing bug in the IPv4 Firewire driver to ensure proper datagram reassembly, it doesn't appear he is using IPv4 Firewire support at all. Rather he originally hit this bug via a static analysis checker and confirmed the behavior with code review.

Firewire cable in front of network switch

Should anyone actually be using IPv4 Firewire in 2026+, the fix was merged this weekend via this pull request ahead of Linux 7.2-rc5 due out later today.

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Linux 7.2-rc5 Released: "Once More We Have Quite A Massive -rc5"010.8626-07-2026
2"KVM Chainsaw" Expected To Hit Linux 7.3 For Dealing With God Data Structure09.826-07-2026
3Fedora 45 Looks To Begin Phasing Out In-Kernel Crypto Userspace API014.2424-07-2026
4Realtek RTL8723B/RTL8723BS Trying To Be Tacked On To The RTW88 Linux Driver010.0626-07-2026
5Imagination PowerVR Driver Marking BXM-4-64 MC1 GPU As Supported In Linux 7.3017.5524-07-2026
6Auto-CPUFreq 3.1 Adds Monitoring Mode To GUI, New Configuration Options & Fixes014.6626-07-2026
7User Frustrations Over The "Tragic State of FreeBSD Audio/Sound" Support04.2526-07-2026
8PyPI hardens package security with new upload restrictions09.5823-07-2026
9GitHub revamps bug bounty program with new VIP tier, payout changes013.3823-07-2026
10KDE Plasma 6.8 Introducing New kscreenctl Tool012.7825-07-2026

Классификация: Информация. Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 10.32. Источник: www.phoronix.com.