ext2: Initialize i_flag after allocation.
We use i_flag to carry some flags like IN_E4INDEX which newer ext2fs variants uses internally. fsck.ext3 rightfully complains after our implementation tags non-directory inodes with INDEX_FL. Initializing i_flag during allocation removes the noise factor and quiets down fsck. Patch from: Damjan Jovanovic PR: 206530
This commit is contained in:
parent
7b40c6df95
commit
e08ad8f068
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=294652
@ -393,6 +393,7 @@ ext2_valloc(struct vnode *pvp, int mode, struct ucred *cred, struct vnode **vpp)
|
||||
* Linux doesn't read the old inode in when it is allocating a
|
||||
* new one. I will set at least i_size and i_blocks to zero.
|
||||
*/
|
||||
ip->i_flag = 0;
|
||||
ip->i_size = 0;
|
||||
ip->i_blocks = 0;
|
||||
ip->i_mode = 0;
|
||||
|
Loading…
Reference in New Issue
Block a user