<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/dev/mlx4, branch releng/12.2</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.2</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.2'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2020-07-13T15:33:06Z</updated>
<entry>
<title>MFC r362953:</title>
<updated>2020-07-13T15:33:06Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-07-13T15:33:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=edff2474e8b747eca2e276bc20b637ea72cafa9b'/>
<id>urn:sha1:edff2474e8b747eca2e276bc20b637ea72cafa9b</id>
<content type='text'>
Infiniband clients must be attached and detached in a specific order in ibcore.

Currently the linking order of the infiniband, IB, modules decide in which
order the clients are attached and detached. For example one IB client may
use resources from another IB client. This can lead to a potential deadlock
at shutdown. For example if the ipoib is unregistered after the ib_multicast
client is detached, then if ipoib is using multicast addresses a deadlock may
happen, because ib_multicast will wait for all its resources to be freed before
returning from the remove method.

Fix this by using module_xxx_order() instead of module_xxx().

Differential Revision:	https://reviews.freebsd.org/D23973
Sponsored by:		Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r362271:</title>
<updated>2020-06-24T05:10:41Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2020-06-24T05:10:41Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5de83306bfa84f66e0d7365fc8a55ac548317944'/>
<id>urn:sha1:5de83306bfa84f66e0d7365fc8a55ac548317944</id>
<content type='text'>
Allow multicast packets to be received in promiscious mode, in mlx4en(4).

Make sure we disable the multicast filter in promiscious mode aswell as when
the all multicast flag is set.

Found by:	Tycho Nightingale &lt;tychon@freebsd.org&gt;
Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r362201:</title>
<updated>2020-06-22T21:28:51Z</updated>
<author>
<name>Ryan Moeller</name>
<email>freqlabs@FreeBSD.org</email>
</author>
<published>2020-06-22T21:28:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=49ea81284416447c8c59ea372120c8ce8ce4880d'/>
<id>urn:sha1:49ea81284416447c8c59ea372120c8ce8ce4880d</id>
<content type='text'>
Avoid trying to toggle TSO twice

Remove TSO from the toggle mask when automatically disabled by TXCKSUM* in
various NIC drivers.

Reviewed by:    hselasky, np, gallatin, jpaetzel
Approved by:    mav (mentor)
Sponsored by:   iXsystems, Inc.
Differential Revision:  https://reviews.freebsd.org/D25120
</content>
</entry>
<entry>
<title>MFC r347325:</title>
<updated>2019-05-16T16:44:40Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2019-05-16T16:44:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=420f9661e8fcd245594855ae7f1b6d747835459b'/>
<id>urn:sha1:420f9661e8fcd245594855ae7f1b6d747835459b</id>
<content type='text'>
Bump the Mellanox driver version numbers and the FreeBSD version number.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r347258:</title>
<updated>2019-05-16T15:49:35Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2019-05-16T15:49:35Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0e9e36729063cccb9b327a21b400311b6fe803fc'/>
<id>urn:sha1:0e9e36729063cccb9b327a21b400311b6fe803fc</id>
<content type='text'>
Make sure to error out when arming the CQ fails in mlx4ib and mlx5ib.

Sponsored by:	Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r345011:</title>
<updated>2019-03-26T13:42:44Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2019-03-26T13:42:44Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e0b5b5c750da49fff3871c648720a1f2d6f0ff24'/>
<id>urn:sha1:e0b5b5c750da49fff3871c648720a1f2d6f0ff24</id>
<content type='text'>
Eliminate useless warning message when reading sysctl node in mlx4core.

Sponsored by:		Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r345010:</title>
<updated>2019-03-26T13:40:33Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2019-03-26T13:40:33Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3c3f1d41fbed30fa123f673d54e7a87067fb667e'/>
<id>urn:sha1:3c3f1d41fbed30fa123f673d54e7a87067fb667e</id>
<content type='text'>
Improve support for switching to and from command polling mode in mlx4core.

Make sure the enter and leave polling routines can be called multiple times
with same setting. Ignore setting polling or event mode twice. This fixes a
deadlock during shutdown if polling mode was already selected.

Sponsored by:		Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r344920:</title>
<updated>2019-03-26T13:37:56Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2019-03-26T13:37:56Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3fa1b3cddcedb011f129af8a059b61a8a18298f0'/>
<id>urn:sha1:3fa1b3cddcedb011f129af8a059b61a8a18298f0</id>
<content type='text'>
Teardown ifnet after stopping port in the mlx4en(4) driver.

mlx4_en_stop_port() calls mlx4_en_put_qp() which can refer the link level
address of the network interface, which in turn will be freed by the
network interface detach function. Make sure the port is stopped
before detaching the network interface.

Sponsored by:		Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r344919:</title>
<updated>2019-03-26T13:33:36Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2019-03-26T13:33:36Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0a2332ff836d918362d6866761bed28e4f110ff3'/>
<id>urn:sha1:0a2332ff836d918362d6866761bed28e4f110ff3</id>
<content type='text'>
Don't hold state lock while detaching network device instance in mlx4en(4).

It can happen during shutdown that the lock will recurse when the mlx4en(4)
instance is part of a lagg interface. Call ether_ifdetach() unlocked.

Backtrace:
panic(): _sx_xlock_hard: recursed on non-recursive sx &amp;mdev-&gt;state_lock
_sx_xlock_hard()
_sx_xlock()
mlx4_en_ioctl()
if_setlladdr()
lagg_port_destroy()
lagg_port_ifdetach()
if_detach()
mlx4_en_destroy_netdev()
mlx4_en_remove()
mlx4_remove_device()
mlx4_unregister_device()
mlx4_unload_one()
mlx4_shutdown()
linux_pci_shutdown()
bus_generic_shutdown()

Sponsored by:		Mellanox Technologies
</content>
</entry>
<entry>
<title>MFC r341587:</title>
<updated>2018-12-12T13:17:49Z</updated>
<author>
<name>Hans Petter Selasky</name>
<email>hselasky@FreeBSD.org</email>
</author>
<published>2018-12-12T13:17:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6d7c00a435ee5f704b427e69af11052cc90bd400'/>
<id>urn:sha1:6d7c00a435ee5f704b427e69af11052cc90bd400</id>
<content type='text'>
mlx4/mlx5: Updated driver version to 3.5.0

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