Leon Romanovsky b79656ed44 RDMA/ipoib: Allow user space differentiate between valid dev_port ... Systemd triggers the following warning during IPoIB device load: mlx5_core 0000:00:0c.0 ib0: "systemd-udevd" wants to know my dev_id. Should it look at dev_port instead? See Documentation/ABI/testing/sysfs-class-net for more info. This is caused due to user space attempt to differentiate old systems without dev_port and new systems with dev_port. In case dev_port will be zero, the systemd will try to read dev_id instead. There is no need to print a warning in such case, because it is valid situation and it is needed to ensure systemd compatibility with old kernels. Link: https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id.c#L358 Cc: <stable@vger.kernel.org> # 4.19 Fixes: f6350da41d ("IB/ipoib: Log sysfs 'dev_id' accesses from userspace") Signed-off-by: Leon Romanovsky <leonro@mellanox.com> Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>		2019-05-07 16:13:23 -03:00
..
ipoib	RDMA/ipoib: Allow user space differentiate between valid dev_port	2019-05-07 16:13:23 -03:00
iser	IB/iser: remove uninitialized variable len	2019-03-27 10:20:33 -03:00
isert	SCSI misc on 20190306	2019-03-09 16:53:47 -08:00
opa_vnic	opa_vnic: fix check on record->event, incorrect operator used	2019-04-08 13:05:24 -03:00
srp	5.1 Merge Window Pull Request	2019-03-09 15:53:03 -08:00
srpt	SCSI misc on 20190306	2019-03-09 16:53:47 -08:00
Makefile	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00