-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: cover more Diag-related code #524
Comments
Hi Matt, I assigned this issue to myself since my colleague Gang Yan in my group is looking at it. |
Thanks! A good task to get familiar with the code and the test suite. Please note that |
Through code coverage analysis, it has been identified that the 'mptcp_diag_dump_one' function lacks test coverage on the testing front. This patch introduces a function in mptcp_sockopt.c, which is built upon the 'inet_diag' module, and integrates it into the 'mptcp_sockopt.sh' to execute the 'mptcp_diag_dump_one' function when server bound a socket. Closes: #524 Signed-off-by: Gang Yan <[email protected]> Message-Id: <[email protected]>
Hi Matt, recently I've been trying to accept and parse messages from kernel, but I've encountered quite a few issues. For instance, when I call recvmsg, I get an 'NLMSG_ERROR' which is 'No such file or directory'. When I change '.nlmsg_flags' to 'NLM_F_REQUEST | NLM_F_DUMP', the error doesn't occur, but this results in the kernel not calling the '.dump_one' interface. Do you have any suggestions? Or do you have any experience with overriding the dump_one method in other modules? |
@Dwyane-Yan no sorry, I'm not sure what is needed here. My understanding is that Also, because the kernel code is not covered by our test suite, it is possible it doesn't work as expected, and also need to be modified. |
There are some improvements that can be done on the tests side to cover more code in some areas (code coverage), e.g. the Diag part:
subflow_get_info_size()
fromdiag.c
is not coveredmptcp_diag_dump_one()
frommptcp_diag.c
is not coveredThe text was updated successfully, but these errors were encountered: