Zach Brown 8b82aa7f18 Consistently initialize inode fields ...

Inode info struct initialization spread out over three places:
 - once for the memory of a slab obect
 - when reading an existing inode from items
 - when initializing a newly allocated inode

Over time field initializtion got out of sync with these rules.  This
makes it more clear which fields get initialized where.  In the inode
info struct we group fields by where there initialized.  We order the
fields by size and location in the inode struct.

Then we make sure that all the initialization sites have everything
covered.  Doing everything in consistent struct order makes it easier
to audit that we haven't missed anything.

What lead to this was realizing that we missed initializing the seqcount
when reading existing inodes.  It should have been initialized in the
slab object constructor.  The 'staging' boolean has the same problem.

Signed-off-by: Zach Brown <zab@versity.com>
Reviewed-by: Mark Fasheh <mfasheh@versity.com>

2017-04-18 14:17:55 -07:00

kmod

Consistently initialize inode fields

2017-04-18 14:17:55 -07:00

S

Description

No description provided

7.7 MiB

Languages

C 86.4%

Shell 10%

Roff 2.5%

TeX 0.8%

Makefile 0.3%