diff options
| author | Jacob Keller <jacob.e.keller@intel.com> | 2020-02-04 15:59:50 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2020-02-05 14:23:20 +0100 |
| commit | d5b90e99e1d51b7b5d2b74fbc4c2db236a510913 (patch) | |
| tree | f4630b4af06e93b1c6ee8863973e1335c74a7be1 /crypto | |
| parent | 33e2b32b5df2b544ac5d43c4de2194bcc822b1b5 (diff) | |
| download | linux-d5b90e99e1d51b7b5d2b74fbc4c2db236a510913.tar.bz2 | |
devlink: report 0 after hitting end in region read
commit fdd41ec21e15 ("devlink: Return right error code in case of errors
for region read") modified the region read code to report errors
properly in unexpected cases.
In the case where the start_offset and ret_offset match, it unilaterally
converted this into an error. This causes an issue for the "dump"
version of the command. In this case, the devlink region dump will
always report an invalid argument:
000000000000ffd0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
000000000000ffe0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
devlink answers: Invalid argument
000000000000fff0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
This occurs because the expected flow for the dump is to return 0 after
there is no further data.
The simplest fix would be to stop converting the error code to -EINVAL
if start_offset == ret_offset. However, avoid unnecessary work by
checking for when start_offset is larger than the region size and
returning 0 upfront.
Fixes: fdd41ec21e15 ("devlink: Return right error code in case of errors for region read")
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Acked-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions