netdev - Re: [RFT net-next 0/6] devlink: expose instance locking and simplify port splitting

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220314114645.5708bf90@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Mon, 14 Mar 2022 11:46:45 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Ido Schimmel <idosch@...sch.org>
Cc:     idosch@...dia.com, petrm@...dia.com, simon.horman@...igine.com,
        netdev@...r.kernel.org, leonro@...dia.com, jiri@...nulli.us,
        Michael Chan <michael.chan@...adcom.com>
Subject: Re: [RFT net-next 0/6] devlink: expose instance locking and
 simplify port splitting

On Thu, 10 Mar 2022 23:13:02 +0200 Ido Schimmel wrote:
> Went over the patches and they look good to me. Thanks again. Will run a
> full regression with them on Sunday.

Hi Ido, no news?

Do you have a preference for these patches getting merged for 5.18 
or waiting after the merge window? IOW I'm wondering if it's more
beneficial for potential backports / out-of-tree builds to have the
ability to lock the devlink instance in 5.18 already or to do as much
of the conversions as possible in a single release (that'd mean waiting
for 5.19)?

If there's no clear preference I'll go for 5.18.

I have the eswitch mode conversion patches almost ready with the
"almost" being mlx5. I may just give up on that one and unlock/lock
in the handler :S