diff options
author | David S. Miller <davem@davemloft.net> | 2018-10-24 14:06:26 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-10-24 14:06:26 -0700 |
commit | 559bf69e3c8f8892c3205417c01cdf8d7823d03c (patch) | |
tree | 6664d41461603de1ddaf5024da60e3d4cfa2a8b5 /block/sed-opal.c | |
parent | 01aa9d518eae8a4d75cd3049defc6ed0b6d0a658 (diff) | |
parent | c63586dc9b3ed5d45ba82e16bf9e2170a55521e6 (diff) | |
download | linux-559bf69e3c8f8892c3205417c01cdf8d7823d03c.tar.gz linux-559bf69e3c8f8892c3205417c01cdf8d7823d03c.tar.bz2 linux-559bf69e3c8f8892c3205417c01cdf8d7823d03c.zip |
Merge branch 'route-dump-filter-fixes'
David Ahern says:
====================
net: Fixups for recent dump filtering changes
Li RongQing noted that tgt_net is leaked in ipv4 due to the recent change
to handle address dumps for a specific device. The report also applies to
ipv6 and other error paths. Patches 1 and 2 fix those leaks.
Patch 3 stops route dumps from erroring out when dumping across address
families and a table id is given. This is needed in preparation for
patch 4.
Patch 4 updates the rtnl_dump_all to handle a failure in one of the dumpit
functions. At the moment, if an address dump returns an error the dump all
loop breaks but the error is dropped. The result can be no data is returned
and no error either leaving the user wondering about the addresses.
Patches were tested with a modified iproute2 to add invalid data to the
dump request causing each specific failure path to be hit in addition
to positive testing that it works as it should when given valid data.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'block/sed-opal.c')
0 files changed, 0 insertions, 0 deletions