[LU-10218] errors not propagated to changelog readers Created: 09/Nov/17 Updated: 14/Dec/17 Resolved: 22/Nov/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.11.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | John Hammond | Assignee: | WC Triage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
Reviewing https://review.whamcloud.com/#/c/29818/ I noticed that errors are not being propagated to changelog readers. I suggest that crs_err be changed to int and the errno associated to any errors encountered be stored there. Then this value can be used in chlg_read() if no records were emitted. Also the return value of chld_load() will also be the return value of kthread_stop() in chlg_release(). clhg_release() should save and return any errors there too. |
| Comments |
| Comment by Gerrit Updater [ 10/Nov/17 ] |
|
John L. Hammond (john.hammond@intel.com) uploaded a new patch: https://review.whamcloud.com/30040 |
| Comment by Gerrit Updater [ 22/Nov/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/30040/ |
| Comment by Peter Jones [ 22/Nov/17 ] |
|
Landed for 2.11 |