-
Notifications
You must be signed in to change notification settings - Fork 5
selftests/bpf: Fix failure path in send_signal test #6342
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
selftests/bpf: Fix failure path in send_signal test #6342
Conversation
|
Upstream branch: 3249e8a |
4eb9670 to
e1b05fd
Compare
|
Upstream branch: f1d8c65 |
09fe11b to
c97bf38
Compare
|
Upstream branch: f1d8c65 |
c97bf38 to
e101866
Compare
e1b05fd to
b1af442
Compare
|
Upstream branch: 93ce3be |
e101866 to
22ae73c
Compare
b1af442 to
67d3dd3
Compare
|
Upstream branch: 93ce3be |
22ae73c to
f301be3
Compare
67d3dd3 to
488318d
Compare
|
Upstream branch: c1da3df |
f301be3 to
2684406
Compare
488318d to
728ac5f
Compare
|
Upstream branch: fea3f5e |
2684406 to
08905cd
Compare
728ac5f to
4fcc7e1
Compare
|
Upstream branch: 63066b7 |
When test_send_signal_kern__open_and_load() fails parent closes the pipe which cases ASSERT_EQ(read(pipe_p2c...)) to fail, but child continues and enters infinite loop, while parent is stuck in wait(NULL). Fix the issue by killing the child before jumping to skel_open_load_failure. The bug was discovered while compiling all of selftests with -O1 instead of -O2 which caused progs/test_send_signal_kern.c to fail to load. Signed-off-by: Alexei Starovoitov <[email protected]> Tested-by: Yonghong Song <[email protected]>
08905cd to
bcad69a
Compare
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=1022813 expired. Closing PR. |
Pull request for series with
subject: selftests/bpf: Fix failure path in send_signal test
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=1022813