Fix struct loststr / struct empobj mismatch corrupting lostitems
The initial parts of struct loststr and struct empobj must match. Commit49780e2c
screwed that up for members lost_uid/uid, which also broke the equivalence of lost_owner/own. Since lost_uid is not used, the former had no effect. But the latter broke xdvisible(). Could make xdump lost leak information. Commita680c811
reorderd struct loststr members to make lost_timestamp equivalent to new struct empobj member timestamp, but failed due to the bug in commit49780e2c
. Commitf33b96b1
then set the timestamp through empobj, which screwed up timestamps in lostitems, i.e. it broke incremental xdump lost. All of the above is in v4.3.12. Commit536ef0b0
(v4.3.15) added lost_seqno / seqno. No effect, because only seqno is used. (cherry picked from commiteb252201b6
)
This commit is contained in:
parent
321d6d74c7
commit
59bdc1cbcc
1 changed files with 1 additions and 1 deletions
|
@ -40,7 +40,7 @@
|
|||
struct loststr {
|
||||
/* initial part must match struct empobj */
|
||||
short ef_type;
|
||||
int lost_uid;
|
||||
short lost_uid;
|
||||
unsigned lost_seqno;
|
||||
time_t lost_timestamp; /* When it was lost */
|
||||
natid lost_owner; /* Who lost it */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue