On Fri, Oct 04, 2019 at 05:46:15PM -0700, Jeff Kirsher wrote:

On Fri, 2019-10-04 at 23:45 +0000, Jason Gunthorpe wrote:

quoted

On Fri, Oct 04, 2019 at 01:12:22PM -0700, Jeff Kirsher wrote:

quoted

quoted

quoted

+	if (ldev->version.major != I40E_CLIENT_VERSION_MAJOR ||
+	    ldev->version.minor != I40E_CLIENT_VERSION_MINOR) {
+		pr_err("version mismatch:\n");
+		pr_err("expected major ver %d, caller specified
major
ver %d\n",
+		       I40E_CLIENT_VERSION_MAJOR, ldev-

quoted

version.major);

+		pr_err("expected minor ver %d, caller specified
minor
ver %d\n",
+		       I40E_CLIENT_VERSION_MINOR, ldev-

quoted

version.minor);

+		return -EINVAL;
+	}

This is can't be in upstream code, we don't support out-of-tree
modules,
everything else will have proper versions.

Who is the "we" in this context?

Upstream sensibility - if we start doing stuff like this then we will
end up doing it everwhere.

I see you cut out the part of my response about Linux distributions
disagreeing with this stance.

quoted

quoted

you support out-of-tree drivers, they do exist and this code would
ensure that if a "out-of-tree" driver is loaded, the driver will do a
sanity check to ensure the RDMA driver will work.

I don't see how this is any different from any of the other myriad of
problems out of tree modules face.

Someone providing out of tree modules has to provide enough parts of
their driver so that it only consumes the stable ABI from the distro
kernel.

Pretty normal stuff really.

Your right, if the dependency was reversed and the out-of-tree (OOT) driver
was dependent upon the RDMA driver, but in this case it is not.  The LAN
driver does not "need" the RDMA driver to work.  So the RDMA driver should
at least check that the LAN driver loaded has the required version to work.

Not in upstream code, there is an expectation that kernel and modules are aligned.

This line of thinking, "marries" the in-kernel RDMA driver with the in-
kernel LAN driver(s) so the end users and Linux distro's can not choose to
upgrade or use any other driver than what comes with the kernel.  I totally
agree that any out-of-tree (OOT) driver needs to make sure they have all
kernel ABI's figured out for whatever kernel they are being installed on.
But what is the problem with the in-kernel RDMA driver to do it's own
checks to ensure the driver it is dependent upon meets its minimum
requirements?

It is packaging problem to ensure that those minimum requirements are in
place.

Similar checks are done in the Intel LAN driver to ensure the firmware is
of a certain level, which is no different than what is being done here.

It doesn't say that it is correct way of doing things. FW is not part
of the kernel hence needs to be checked. Modules are different from
FW because they are part of the distributed kernel.

Thanks