Message ID | 20220111175438.21901-1-sthemmin@microsoft.com (mailing list archive) |
---|---|
Headers | show |
Series | clang warning fixes | expand |
On 1/11/22 10:54 AM, Stephen Hemminger wrote: > This patch set makes iproute2-next main branch compile without warnings > on Clang 11 (and probably later versions). > > Still needs more testing before merge. There are likely to be some > unnecessary output format changes from this. > I think the tc patches are the only likely candidates. The print_string_name_value conversion should be clean. Jamal: As I recall you have a test suite for tc. Can you test this set?
On Sun, 16 Jan 2022 16:18:53 -0700 David Ahern <dsahern@gmail.com> wrote: > On 1/11/22 10:54 AM, Stephen Hemminger wrote: > > This patch set makes iproute2-next main branch compile without warnings > > on Clang 11 (and probably later versions). > > > > Still needs more testing before merge. There are likely to be some > > unnecessary output format changes from this. > > > > I think the tc patches are the only likely candidates. The > print_string_name_value conversion should be clean. > > Jamal: As I recall you have a test suite for tc. Can you test this set? There was a blank after newline and with print_string_name_value that goes away. Lets introduce something like print_nl_indent() to handle that
On 2022-01-16 18:18, David Ahern wrote: > On 1/11/22 10:54 AM, Stephen Hemminger wrote: >> This patch set makes iproute2-next main branch compile without warnings >> on Clang 11 (and probably later versions). >> >> Still needs more testing before merge. There are likely to be some >> unnecessary output format changes from this. >> > > I think the tc patches are the only likely candidates. The > print_string_name_value conversion should be clean. > > Jamal: As I recall you have a test suite for tc. Can you test this set? We try to push, whenever we can, to kernel tdc tests. The Intel robot should catch issues based on what we have there. If we make part of the acceptance process (incumbent on people who create the patches) to run those tests it would help getting cleaner submissions. Not sure if we can have a bot doing this.. Punting to Victor(on Cc) to run the tests and double check if we have test cases that cover for these changes. cheers, jamal
Hi, Sorry for not responding sooner. I patched iproute2 and several existing tests failed. Example: Test 696a: Add simple ct action All test results: 1..1 not ok 1 696a - Add simple ct action Could not match regex pattern. Verify command output: total acts 1 action order 0: ct zone 0 pipe index 42 ref 1 bind 0 The problem is the additional new line added. WIthout this patch: https://patchwork.kernel.org/project/netdevbpf/patch/20220117175019.13993-6-stephen@networkplumber.org/ it the output of tc actions list action ct is: total acts 1 action order 0: ct zone 0 pipe index 42 ref 1 bind 0 With it it is: total acts 1 action order 0: ct zone 0 pipe index 42 ref 1 bind 0 So I believe the problem is just formatting, however it still breaks some tests cheers, Victor On 17 Jan 2022, at 12:29, Jamal Hadi Salim <jhs@mojatatu.com> wrote: On 2022-01-16 18:18, David Ahern wrote: On 1/11/22 10:54 AM, Stephen Hemminger wrote: This patch set makes iproute2-next main branch compile without warnings on Clang 11 (and probably later versions). Still needs more testing before merge. There are likely to be some unnecessary output format changes from this. I think the tc patches are the only likely candidates. The print_string_name_value conversion should be clean. Jamal: As I recall you have a test suite for tc. Can you test this set? We try to push, whenever we can, to kernel tdc tests. The Intel robot should catch issues based on what we have there. If we make part of the acceptance process (incumbent on people who create the patches) to run those tests it would help getting cleaner submissions. Not sure if we can have a bot doing this.. Punting to Victor(on Cc) to run the tests and double check if we have test cases that cover for these changes. cheers, jamal
On 1/20/22 5:48 AM, Victor Nogueira wrote: > Hi, > Sorry for not responding sooner. I patched iproute2 and several > existing tests failed. > Example: > Test 696a: Add simple ct action > > All test results: > > 1..1 > not ok 1 696a - Add simple ct action > Could not match regex pattern. Verify command output: > total acts 1 > > action order 0: ct > zone 0 pipe > index 42 ref 1 bind 0 > > The problem is the additional new line added. > > WIthout this patch: > https://patchwork.kernel.org/project/netdevbpf/patch/20220117175019.13993-6-stephen@networkplumber.org/ > it the output of tc actions list action ct is: > > total acts 1 > > action order 0: ct zone 0 pipe > index 42 ref 1 bind 0 > > With it it is: > > total acts 1 > > action order 0: ct > zone 0 pipe > index 42 ref 1 bind 0 > > So I believe the problem is just formatting, however it still breaks some tests > Thanks, Victor. Hopefully that is addressed in v3 of the set.
On Thu, Jan 20, 2022 at 4:20 PM David Ahern <dsahern@gmail.com> wrote: > > On 1/20/22 5:48 AM, Victor Nogueira wrote: > > Hi, > > Sorry for not responding sooner. I patched iproute2 and several > > existing tests failed. > > Example: > > Test 696a: Add simple ct action > > > > All test results: > > > > 1..1 > > not ok 1 696a - Add simple ct action > > Could not match regex pattern. Verify command output: > > total acts 1 > > > > action order 0: ct > > zone 0 pipe > > index 42 ref 1 bind 0 > > > > The problem is the additional new line added. > > > > WIthout this patch: > > https://patchwork.kernel.org/project/netdevbpf/patch/20220117175019.13993-6-stephen@networkplumber.org/ > > it the output of tc actions list action ct is: > > > > total acts 1 > > > > action order 0: ct zone 0 pipe > > index 42 ref 1 bind 0 > > > > With it it is: > > > > total acts 1 > > > > action order 0: ct > > zone 0 pipe > > index 42 ref 1 bind 0 > > > > So I believe the problem is just formatting, however it still breaks some tests > > > > Thanks, Victor. Hopefully that is addressed in v3 of the set. > Actually, I tested using v3 patches. Sorry, I should've said that in the previous email. cheers, Victor