[LU-10170] OSP device could miss wakeup from committed sync Created: 30/Oct/17 Updated: 18/Dec/17 Resolved: 18/Dec/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jinshan Xiong (Inactive) | Assignee: | Jinshan Xiong (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Severity: | 3 | ||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||
| Description |
|
In the current implementation of osp_sync_add_rec(), it adds the osp_device into the wakeup list before inserting the actual record. However, if the OSP device is woken up and taken out of the list by a previous committed sync change, it will miss the wakeup for the recent sync change and then setattr RPC to OST would never be sent. |
| Comments |
| Comment by Gerrit Updater [ 30/Oct/17 ] |
|
Jinshan Xiong (jinshan.xiong@intel.com) uploaded a new patch: https://review.whamcloud.com/29854 |