<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/sys, branch stable/10</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=stable%2F10</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=stable%2F10'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2020-06-19T07:07:10Z</updated>
<entry>
<title>MFC r362078:</title>
<updated>2020-06-19T07:07:10Z</updated>
<author>
<name>Ravi Pokala</name>
<email>rpokala@FreeBSD.org</email>
</author>
<published>2020-06-19T07:07:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=8cebe0d35ca72b1a823e0a129bd08f60407b340d'/>
<id>urn:sha1:8cebe0d35ca72b1a823e0a129bd08f60407b340d</id>
<content type='text'>
Decode the "LACP Fast Timeout" LAGG option flag

r286700 added the "lacp_fast_timeout" option to `ifconfig', but we forgot to
include the new option in the string used to decode the option bits. Add
"LACP_FAST_TIMO" to LAGG_OPT_BITS.

Also, s/LAGG_OPT_LACP_TIMEOUT/LAGG_OPT_LACP_FAST_TIMO/g , to be clearer that
the flag indicates "Fast Timeout" mode.
</content>
</entry>
<entry>
<title>MFC r362045:</title>
<updated>2020-06-18T10:41:51Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-18T10:41:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=1ae4bac217163b0cfd834213dbe1d64464baef5b'/>
<id>urn:sha1:1ae4bac217163b0cfd834213dbe1d64464baef5b</id>
<content type='text'>
Make sure packets generated by raw IP code is let through by mlx5en(4).

Allow the TCP header to reside in the mbuf following the IP header.
Else such packets will get dropped.

Backtrace:
mlx5e_sq_xmit()
mlx5e_xmit()
ether_output_frame()
ether_output()
ip_output_send()
ip_output()
rip_output()
sosend_generic()
sosend()
kern_sendit()
sendit()
sys_sendto()
amd64_syscall()
fast_syscall_common()

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r362044:</title>
<updated>2020-06-18T10:31:21Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-18T10:31:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=e5fce44e5127a0f7454203b837487cf86986fc55'/>
<id>urn:sha1:e5fce44e5127a0f7454203b837487cf86986fc55</id>
<content type='text'>
Extend use of unlikely() in the fast path, in mlx5en(4).

Typically the TCP/IP headers fit within the first mbuf and should not
trigger any of the error cases. Use unlikely() for these cases.

No functional change.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r362043:</title>
<updated>2020-06-18T10:17:36Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-18T10:17:36Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=73356f025754fa313d4aab17a2afc0acc41e9c0d'/>
<id>urn:sha1:73356f025754fa313d4aab17a2afc0acc41e9c0d</id>
<content type='text'>
Use const keyword when parsing the TCP/IP header in the fast path in mlx5en(4).

When parsing the TCP/IP header in the fast path, make it clear by using
the const keyword, no fields are to be modified inside the transmitted
packet.

No functional change.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r362056:</title>
<updated>2020-06-14T05:33:25Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-14T05:33:25Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=0be584a9496934fd6c9b029a1da757363be30d5c'/>
<id>urn:sha1:0be584a9496934fd6c9b029a1da757363be30d5c</id>
<content type='text'>
Add missing range checks when receiving USB ethernet packets.

Found by:	Ilja Van Sprundel, IOActive
Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361827:</title>
<updated>2020-06-08T09:34:16Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-08T09:34:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=1036bfa7dd4ecac232c91779e9096d3744885f3e'/>
<id>urn:sha1:1036bfa7dd4ecac232c91779e9096d3744885f3e</id>
<content type='text'>
USB HID descriptors may push/pop the current state to allow
description of items residing in a so-called union. FreeBSD currently
only supports 4 such push levels.

If the push level is not restored within the processing of the same
HID item, an invalid memory location may be used for subsequent HID
item processing.

Verify that the push level is always valid when processing HID items.

Reported by:	Andy Nguyen (Google)
Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361582:</title>
<updated>2020-06-08T09:31:14Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-08T09:31:14Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=a879f39e0f5fe80e3e332fecd2fcf5c9c1731cd0'/>
<id>urn:sha1:a879f39e0f5fe80e3e332fecd2fcf5c9c1731cd0</id>
<content type='text'>
Fix check for wMaxPacketSize in USB bluetooth driver,
in case device is not FULL speed.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361581:</title>
<updated>2020-06-08T09:28:26Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-08T09:28:26Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=ed33b8c8a505b702a9183482b1d61c7d0b315944'/>
<id>urn:sha1:ed33b8c8a505b702a9183482b1d61c7d0b315944</id>
<content type='text'>
Implement helper function, usbd_get_max_frame_length(), which allows kernel
device drivers to correctly predict the default USB transfer frame length.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361577:</title>
<updated>2020-06-08T09:25:01Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-08T09:25:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=8e51c3499e0273806331f4172c5db90b061734e0'/>
<id>urn:sha1:8e51c3499e0273806331f4172c5db90b061734e0</id>
<content type='text'>
Don't allow USB device drivers to parent own interface.
It will prevent proper USB device detach.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r361075:</title>
<updated>2020-05-22T09:01:26Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-05-22T09:01:26Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=ced76afa5b2b1b529b0e5271528237119f92a5b0'/>
<id>urn:sha1:ced76afa5b2b1b529b0e5271528237119f92a5b0</id>
<content type='text'>
Assign process group of the TTY under the "proctree_lock".

This fixes a race where concurrent calls to doenterpgrp() and
leavepgrp() while TIOCSCTTY is executing may result in tp-&gt;t_pgrp
changing value so that tty_rel_pgrp() misses clearing it to NULL. For
more details refer to the use of pgdelete() in the kernel.

No functional change intended.

Panic backtrace:
__mtx_lock_sleep() # page fault due to using destroyed mutex
tty_signal_pgrp()
tty_ioctl()
ptsdev_ioctl()
kern_ioctl()
sys_ioctl()
amd64_syscall()

Sponsored by:	Mellanox Technologies
</content>
</entry>
</feed>
