[LU-16554] OUT UPDATE REPLY is always 4KiB on wire Created: 14/Feb/23 Updated: 04/Apr/23 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.16.0 |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Nathaniel Clark | Assignee: | Vitaliy Kuznetsov |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
OUT UPDATE Request always lists reply size as 4K in out_update_header (lustre/osp/osp_trans.c::osp_prep_update_req()) OUT UPDATE Reply blindly uses this size to create the pack size, not actually checking the size of the packed reply. lustre/target/out_handler.c::out_handle()) If the former behavior is changed, than the later behavior will break. Currently there's a 4K buffer to hold ~100B of data.
|
| Comments |
| Comment by Gerrit Updater [ 04/Apr/23 ] |
|
"Vitaliy Kuznetsov <vkuznetsov@ddn.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/50522 |