[LU-2095] Trival fix for lustre/utils/wiretest.c Created: 05/Oct/12  Updated: 08/Oct/12  Resolved: 08/Oct/12

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.4.0
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: Keith Mannthey (Inactive) Assignee: Keith Mannthey (Inactive)
Resolution: Not a Bug Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 4378

 Description   

Trivial fix for lustre/utils/wiretest.c



 Comments   
Comment by Andreas Dilger [ 06/Oct/12 ]

Sorry, but coming here from the patch to find out the reason behind the patch, I don't find anything of use. Even if the change were trivial (which in this case it is not, and would have potentially been a serious problem in the network protocol) the patch and bug deserve a clear explanation of what is being fixed, and why it is trivial.

I think that you might have missed the extra zero at the end of the OBD_CONNECT_LIGHTWEIGHT definition (0x1000000000000ULL), and thought it conflicted with OBD_CONNECT_GRANT_PARAM, which is 0x100000000000ULL? Having that kind of explanation in the bug and/or the commit comment would make your reasoning clear.

Comment by Keith Mannthey (Inactive) [ 08/Oct/12 ]

Sorry this got on your radar, I will take more care in the future. I was reviewing another patch in this same code area and noticed that the params had skipped order yet were still in the same logical block and that logic was being extended. A little while later I had seen that this also appeared in another wiretest.c and was going to abandon the change to take a bit better look at the situation. I see that it would have caused quite a problem.

It was per-mature for me to submit a patch and I knew it not too long after pushing it via git. I should have invested a bit more time to carefully review the situation before the initial submission.

Generated at Sat Feb 10 01:22:19 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.