[LU-8084] namespace LFSCK needs to handle linkea record length properly Created: 29/Apr/16 Updated: 14/Jun/18 Resolved: 22/Aug/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.9.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | nasf (Inactive) | Assignee: | nasf (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
The record length in the linkea may be corrupted. If we do not handle the invalid record length when locate the next linkea record or delete the current record, it may cause invalid memory accessing and corrupt other data in RAM, and then cause kinds of strange RAM issues. |
| Comments |
| Comment by Gerrit Updater [ 29/Apr/16 ] |
|
Fan Yong (fan.yong@intel.com) uploaded a new patch: http://review.whamcloud.com/19877 |
| Comment by Gerrit Updater [ 22/Aug/16 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/19877/ |
| Comment by nasf (Inactive) [ 22/Aug/16 ] |
|
The patch has been landed to master. |