linux-kernel - RE: [PATCH rdma-next v2 0/4] RDMA/mana_ib: allow separate mana

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID:
 <SA6PR21MB4231180CF3D14B3FDFF4E5C2CE872@SA6PR21MB4231.namprd21.prod.outlook.com>
Date: Sat, 26 Apr 2025 17:30:20 +0000
From: Long Li <longli@...rosoft.com>
To: Konstantin Taranov <kotaranov@...ux.microsoft.com>, Konstantin Taranov
	<kotaranov@...rosoft.com>, "pabeni@...hat.com" <pabeni@...hat.com>, Haiyang
 Zhang <haiyangz@...rosoft.com>, KY Srinivasan <kys@...rosoft.com>,
	"edumazet@...gle.com" <edumazet@...gle.com>, "kuba@...nel.org"
	<kuba@...nel.org>, "davem@...emloft.net" <davem@...emloft.net>, Dexuan Cui
	<decui@...rosoft.com>, "wei.liu@...nel.org" <wei.liu@...nel.org>,
	"jgg@...pe.ca" <jgg@...pe.ca>, "leon@...nel.org" <leon@...nel.org>
CC: "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH rdma-next v2 0/4] RDMA/mana_ib: allow separate mana_ib for
 each mana client

> Subject: [PATCH rdma-next v2 0/4] RDMA/mana_ib: allow separate mana_ib for
> each mana client
> 
> Microsoft mana adapter has 2 devices in the HW: mana ethernet device and
> RNIC device.
> Both devices can implement RDMA drivers and, so far, they have been sharing
> one ib device context. However, they are different devices with different
> capabilities in the HW and have different lifetime model.
> 
> This series allows us to model the aforementioned two devices as separate ib
> devices.
> The mana_ib will continue supporting two devices but as individual ib devices.
> It enables the driver to dynamically destroy and create the auxiliary device over
> RNIC, when the HW reboots the RNIC module. Without this separation, the
> reboot would cause destruction of the ib device serving DPDK clients from the
> uninterrupted ethernet HW module.

There are test failures. Please ignore this patch set.

Thanks,
Long