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
| ||
|
Date: Wed, 8 Sep 2021 09:39:59 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Saeed Mahameed <saeed@...nel.org> Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org, Aya Levin <ayal@...dia.com>, Tariq Toukan <tariqt@...dia.com>, Saeed Mahameed <saeedm@...dia.com> Subject: Re: [net 7/7] net/mlx5e: Fix condition when retrieving PTP-rqn On Tue, 7 Sep 2021 14:24:20 -0700 Saeed Mahameed wrote: > From: Aya Levin <ayal@...dia.com> > > When activating the PTP-RQ, redirect the RQT from drop-RQ to PTP-RQ. > Use mlx5e_channels_get_ptp_rqn to retrieve the rqn. This helper returns > a boolean (not status), hence caller should consider return value 0 as a > fail. Change the caller interpretation of the return value. It would be really great to turn down the dial on the abbreviations and add some user-visible impact, as is best practice (some would say a requirement) for fixes. I've been following the PTP work in mlx5 a little bit but I have no idea what a RQT is and what kind of issues to expect without this patch.
Powered by blists - more mailing lists