Library Name | xfsprogs |
---|---|
Version #1 | 3.1.11 |
Version #2 | 3.2.0 |
CPU Type | x86 |
GCC Version | 4.6.1 |
Total Header Files | 59 |
---|---|
Total Shared Libraries | 10 |
Total Symbols / Types | 340 / 359 |
Verdict | Incompatible (65.3%) |
Severity | Count | |
---|---|---|
Added Symbols | - | 101 |
Removed Symbols | High | 48 |
Problems with Data Types | High | 7 |
Medium | 28 | |
Low | 92 | |
Problems with Symbols | High | 32 |
Medium | 31 | |
Low | 38 | |
Problems with Constants | Low | 52 |
Other Changes in Constants | - | 79 |
Change | Effect | |
---|---|---|
1 | Field m_dev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field m_logdev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | Field m_reservations has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
4 | Field m_rtdev has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field if_lastex has been removed from the middle position of this structural type. | 1) Previous accesses of applications to the removed field will be incorrect. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 8 bytes to 4 bytes. | Layout of parameter's stack of several functions has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 8 bytes to 4 bytes. | Layout of parameter's stack of several functions has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | 1st parameter p1 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from dev_t (8 bytes) to struct xfs_buftarg* (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | The pointer level of 1st parameter p1 has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from dev_t (8 bytes) to struct xfs_buftarg* (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | The pointer level of 1st parameter p1 has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from dev_t (8 bytes) to struct xfs_buftarg* (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | The pointer level of 1st parameter p1 has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from dev_t (8 bytes) to struct xfs_buftarg* (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | The pointer level of 1st parameter p1 has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from dev_t (8 bytes) to struct xfs_buftarg* (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | The pointer level of 1st parameter p1 has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
Change | Effect | |
---|---|---|
1 | 1st parameter p1 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | Middle parameter p1 of type dev_t has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from dev_t (8 bytes) to struct xfs_buftarg* (4 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | The pointer level of 1st parameter p1 has been increased from 0 to 1. | The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications. |
Change | Effect | |
---|---|---|
1 | 1st parameter p1 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 2nd parameter p2 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
3 | Middle parameter p1 of type xfs_trans_t* has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
4 | Middle parameter p2 of type uint has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
5 | Middle parameter p3 of type uint has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
6 | Middle parameter p4 of type uint has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | 1st parameter p1 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | 2nd parameter p2 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
3 | 4th parameter p4 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
4 | 5th parameter p5 has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
5 | 1st middle parameter mp has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
6 | 2nd middle parameter tp has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
7 | 4th middle parameter bpp has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
8 | 5th middle parameter buf_flags has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Parameter mapped_bno of type xfs_daddr_t has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | 6th middle parameter alloc_done has been removed from the calling stack. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
2 | Type of 3rd parameter mode has been changed from mode_t (4 bytes) to umode_t (2 bytes). | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Field c_flags has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field c_hashshift has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Field b_dev has been removed from this type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
Change | Effect | |
---|---|---|
1 | Size of field i_d has been changed from 96 bytes to 176 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
2 | Size of field i_df has been changed from 56 bytes to 52 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
3 | Type of field i_dev has been changed from dev_t (8 bytes) to struct xfs_buftarg (12 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Field ili_fields has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Size of field ili_item has been changed from 12 bytes to 20 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Field m_logdev_targp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
2 | Field m_resv has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
3 | Field m_rtdev_targp has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
4 | Size of field m_sb has been changed from 208 bytes to 248 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
5 | Type of field m_inode_cluster_size has been changed from __uint16_t (2 bytes) to uint (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field fsbno has been changed from 8 bytes to 4 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
2 | Size of field firstblock has been changed from 8 bytes to 4 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field xbfi_startblock has been changed from 8 bytes to 4 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field br_startblock has been changed from 8 bytes to 4 bytes. | Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field bb_u has been changed from 16 bytes to 64 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field bc_rec has been changed from 28 bytes to 24 bytes. | Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field l has been changed from 16 bytes to 64 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
2 | Size of field s has been changed from 8 bytes to 48 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Size of field b has been changed from 28 bytes to 24 bytes. | Previous accesses of applications and library functions to this field may be broken. |
Change | Effect | |
---|---|---|
1 | Field filetype has been added at the middle position of this structural type. | 1) Size of the inclusive type has been changed. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | Type of field name has been changed from __u8[1] (1 byte) to __u8[] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
2 | Field tag has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | Field if_ext_max has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
Change | Effect | |
---|---|---|
1 | The relative position of field lid_trans has been changed from 2 to 1. | Applications will access incorrect memory when attempting to access this field. |
2 | Field lid_size has been removed from the middle position of this structural type. | 1) Applications will access incorrect memory when attempting to access this field. 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
Change | Effect | |
---|---|---|
1 | 5th parameter p5 has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter p5 of type uint has been removed from the calling stack. | This parameter will be ignored by the function. |
2 | Parameter p6 of type uint has been removed from the calling stack. | This parameter will be ignored by the function. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 136 bytes to 144 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter log has been changed from struct log (100 bytes) to struct xlog (96 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter log has been changed from struct log (100 bytes) to struct xlog (96 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter log has been changed from struct log (100 bytes) to struct xlog (96 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter log has been changed from struct log (100 bytes) to struct xlog (96 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter log has been changed from struct log (100 bytes) to struct xlog (96 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter log has been changed from struct log (100 bytes) to struct xlog (96 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter p1 has been changed from struct log (100 bytes) to struct xlog (96 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter leaf1_bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
2 | Base type of 2nd parameter leaf2_bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter p1 has been changed from struct xfs_mount (540 bytes) to struct xfs_inode (340 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Parameter ops of type struct xfs_buf_ops const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Base type of 5th parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 5th parameter bpp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
2 | Parameter ops of type struct xfs_buf_ops const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Parameter ops of type struct xfs_buf_ops const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
Change | Effect | |
---|---|---|
1 | Base type of 3rd parameter dead_buf has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 3rd parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Size of this global data has been changed from 8 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
Change | Effect | |
---|---|---|
1 | Base type of 1st parameter d has been changed from struct xfs_dir2_data (28 bytes) to struct xfs_dir2_data_hdr (16 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 2nd parameter d has been changed from struct xfs_dir2_data (28 bytes) to struct xfs_dir2_data_hdr (16 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 2nd parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 2nd parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 2nd parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 2nd parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Base type of 2nd parameter bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | This parameter may be incorrectly initialized by applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 660 bytes to 668 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Base type has been changed from unsigned int(*)(cache_key_t,unsigned int) to unsigned int(*)(cache_key_t,unsigned int,unsigned int). | Replacement of the base data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Field bcache_flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field icache_flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Size of this type has been changed from 136 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field b_length has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field b_map has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field b_nmaps has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field b_ops has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field b_pag has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Field b_target has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
7 | Field b_fspriv has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
8 | Size of this type has been changed from 128 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
9 | Field b_fsprivate has been removed from this type. | Size of the inclusive type has been changed. |
10 | Type of field b_addr has been changed from char* to void*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
11 | Field b_blkno has been renamed to b_bn. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 260 bytes to 340 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 80 bytes to 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field li_lsn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 12 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field m_quotainfo has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 540 bytes to 832 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
3 | Field m_rootip has been renamed to m_ddev_targp. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 88 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 16 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 28 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 24 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field bb_blkno has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field bb_crc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field bb_lsn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field bb_owner has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field bb_uuid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Size of this type has been changed from 8 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field bb_blkno has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field bb_crc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field bb_lsn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field bb_owner has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field bb_pad has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Field bb_uuid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
7 | Size of this type has been changed from 16 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 148 bytes to 140 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Size of field bc_private has been changed from 24 bytes to 20 bytes. | Size of the inclusive type has been changed. |
Change | Effect | |
---|---|---|
1 | Field buf_ops has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 64 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 16 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 28 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 96 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Base type of field bp has been changed from struct xfs_dabuf (16 bytes) to struct xfs_buf (144 bytes). | Possible access of applications to incorrect memory through the pointer. |
Change | Effect | |
---|---|---|
1 | Field di_changecount has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field di_crc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field di_crtime has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field di_flags2 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field di_ino has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Field di_lsn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
7 | Field di_uuid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
8 | Field di_pad2 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
9 | Size of this type has been changed from 100 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field di_changecount has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field di_crc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field di_crtime has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field di_flags2 has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field di_ino has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Field di_lsn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
7 | Field di_next_unlinked has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
8 | Field di_uuid has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
9 | Field di_pad2 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
10 | Size of this type has been changed from 96 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 56 bytes to 52 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field h_chksum has been renamed to h_crc. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
Change | Effect | |
---|---|---|
1 | Field sb_crc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field sb_features_compat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field sb_features_incompat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field sb_features_log_incompat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field sb_features_ro_compat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Field sb_lsn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
7 | Field sb_pad has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
8 | Field sb_pquotino has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
9 | Size of this type has been changed from 208 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field sb_crc has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Field sb_features_compat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
3 | Field sb_features_incompat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
4 | Field sb_features_log_incompat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
5 | Field sb_features_ro_compat has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
6 | Field sb_lsn has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
7 | Field sb_pad has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
8 | Field sb_pquotino has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
9 | Size of this type has been changed from 208 bytes to 248 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Field type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
2 | Size of this type has been changed from 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
Change | Effect | |
---|---|---|
1 | Size of this type has been changed from 8 bytes to 4 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
2 | Base type has been changed from unsigned long long to unsigned int. | Replacement of the base data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Base type has been changed from unsigned long long to unsigned int. | Replacement of the base data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter flist has been changed from xfs_bmap_free_t* to struct xfs_bmap_free*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter flist has been changed from xfs_bmap_free_t* to struct xfs_bmap_free*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 8th parameter flist has been changed from xfs_bmap_free_t* to struct xfs_bmap_free*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 3rd parameter vp has been renamed to r. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 3rd parameter vp has been renamed to r. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 1st parameter d has been renamed to hdr. | Renaming of a parameter may indicate a change in its semantic meaning. |
2 | Type of 2nd parameter dup has been changed from xfs_dir2_data_unused_t* to struct xfs_dir2_data_unused*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
3 | Type of return value has been changed from xfs_dir2_data_free_t* to struct xfs_dir2_data_free*. | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | 2nd parameter d has been renamed to hdr. | Renaming of a parameter may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter dep has been changed from xfs_dir2_data_entry_t* to struct xfs_dir2_data_entry*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter dup has been changed from xfs_dir2_data_unused_t* to struct xfs_dir2_data_unused*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 3rd parameter dup has been changed from xfs_dir2_data_unused_t* to struct xfs_dir2_data_unused*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of return value has been changed from xfs_bmbt_rec_host_t* to struct xfs_bmbt_rec_host*. | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of return value has been changed from xfs_ext_irec_t* to struct xfs_ext_irec*. | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of return value has been changed from xfs_bmbt_rec_host_t* to struct xfs_bmbt_rec_host*. | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of return value has been changed from xfs_ext_irec_t* to struct xfs_ext_irec*. | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 4th parameter p4 has been changed from xfs_bmbt_irec_t* to struct xfs_bmbt_irec*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
2 | Type of return value has been changed from xfs_ext_irec_t* to struct xfs_ext_irec*. | Replacement of return type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 1st parameter p1 has been changed from xfs_ifork_t* to struct xfs_ifork*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | Type of 2nd parameter p2 has been changed from xfs_bmbt_rec_t* to struct xfs_bmbt_rec*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
Change | Effect | |
---|---|---|
1 | The value of constant LIBXFS_MOUNT_32BITINODES has been changed from 0x0004 to 0x0002. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant LIBXFS_MOUNT_32BITINOOPT has been changed from 0x0008 to 0x0004. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant LIBXFS_MOUNT_ATTR2 has been changed from 0x0020 to 0x0010. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant LIBXFS_MOUNT_COMPAT_ATTR has been changed from 0x0010 to 0x0008. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant LIBXFS_MOUNT_DEBUGGER has been changed from 0x0002 to 0x0001. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant LIBXFS_MOUNT_ROOTINOS with value 0x0001 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_AGF_NUM_BITS has been changed from 12 to 13. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant XFS_PAGB_NUM_SLOTS with value 128 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BMAPI_ATTRFORK has been changed from 0x010 to 0x004. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BMAPI_CONTIG has been changed from 0x100 to 0x020. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BMAPI_CONVERT has been changed from 0x200 to 0x040. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BMAPI_DELAY with value 0x002 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BMAPI_ENTIRE has been changed from 0x004 to 0x001. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BMAPI_IGSTATE has been changed from 0x080 to 0x010. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BMAPI_METADATA has been changed from 0x008 to 0x002. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BMAPI_PREALLOC has been changed from 0x040 to 0x008. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BMAPI_RSVBLOCKS with value 0x020 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BMAPI_WRITE with value 0x001 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BB_LEFTSIB has been changed from 0x08 to (1 << 3). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BB_LEVEL has been changed from 0x02 to (1 << 1). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BB_MAGIC has been changed from 0x01 to (1 << 0). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BB_NUMRECS has been changed from 0x04 to (1 << 2). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BB_RIGHTSIB has been changed from 0x10 to (1 << 4). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLF_CANCEL has been changed from 0x2 to (1<<1). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLF_GDQUOT_BUF has been changed from 0x10 to (1<<4). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLF_INODE_BUF has been changed from 0x1 to (1<<0). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLF_PDQUOT_BUF has been changed from 0x8 to (1<<3). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLF_UDQUOT_BUF has been changed from 0x4 to (1<<2). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLI_DIRTY has been changed from 0x02 to (1<<0). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLI_HOLD has been changed from 0x01 to (1<<1). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLI_INODE_ALLOC_BUF has been changed from 0x10 to (1<<3). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BLI_INODE_BUF with value 0x40 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BLI_LOGGED with value 0x08 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_BLI_STALE has been changed from 0x04 to (1<<2). | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BLI_STALE_INODE with value 0x20 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR_LEAF_MAGIC with value 0xfeeb has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR_LEAF_MAPSIZE with value 3 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XFS_IGET_CREATE with value 0x1 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XFS_IGET_UNTRUSTED with value 0x2 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XLOG_REG_TYPE_MAX has been changed from 19 to 20. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant XLOG_ACTIVE_RECOVERY with value 0x2 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XLOG_CHKSUM_MISMATCH with value 0x1 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XLOG_IO_ERROR with value 0x8 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XLOG_RECOVERY_NEEDED with value 0x4 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DQ_INACTIVE with value 0x0020 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DQ_WANT with value 0x0010 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_GQUOTA_ACTIVE has been changed from 0x0400 to 0x2000. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_PQUOTA_ACTIVE has been changed from 0x0200 to 0x4000. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant XFS_QMOPT_DQSUSER with value 0x0000020 has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_UQUOTA_ACTIVE has been changed from 0x0100 to 0x1000. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant XFS_TRANS_MAGIC with value 0x5452414E has been removed. | The value of this constant may no longer be properly handled by new-version library functions. |
Change | Effect | |
---|---|---|
1 | The value of constant XFS_TRANS_TYPE_MAX has been changed from 42 to 43. | Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications. |
Change | Effect | |
---|---|---|
1 | The constant CACHE_HIT with value 0 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant CACHE_MISCOMPARE_PURGE with value (1 << 0) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant CACHE_MISS with value 1 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant CACHE_PURGE with value 2 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant b_dev with value b_target->dev has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XB_PAGES with value 2 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BUF_DADDR_NULL with value ((xfs_daddr_t) (-1LL)) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_AGF_UUID with value 0x00001000 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_AGFL_MAGIC with value 0x5841464c has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_ICI_EOFBLOCKS_TAG with value 1 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BMAPI_STACK_SWITCH with value 0x080 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BB_ALL_BITS_CRC with value ((1 << XFS_BB_NUM_BITS_CRC) - 1) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BB_BLKNO with value (1 << 5) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BB_LSN with value (1 << 6) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BB_NUM_BITS_CRC with value 9 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BB_OWNER with value (1 << 8) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BB_UUID with value (1 << 7) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BTREE_CRC_BLOCKS with value (1<<3) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_CRC_SEED with value (~(__uint32_t)0) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_ATTR3_LEAF_MAGIC with value 0x3bee has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_ATTR3_RMT_MAGIC with value 0x5841524d has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DA3_NODE_MAGIC with value 0x3ebe has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_BLOCK_MAGIC with value 0x58444233 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_DATA_MAGIC with value 0x58444433 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FREE_MAGIC with value 0x58444633 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_BLKDEV with value 4 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_CHRDEV with value 3 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_DIR with value 2 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_FIFO with value 5 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_MAX with value 9 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_REG_FILE with value 1 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_SOCK with value 6 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_SYMLINK with value 7 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_UNKNOWN with value 0 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_FT_WHT with value 8 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_LEAF1_MAGIC with value 0x3df1 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DIR3_LEAFN_MAGIC with value 0x3dff has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant S_SHIFT with value 12 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_ABTB_CRC_MAGIC with value 0x41423342 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_ABTC_CRC_MAGIC with value 0x41423343 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BMAP_CRC_MAGIC with value 0x424d4133 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_IBT_CRC_MAGIC with value 0x49414233 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SYMLINK_MAGIC with value 0x58534c4d has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SYMLINK_MAPS with value 3 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_EOF_FLAGS_GID with value (1 << 2) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_EOF_FLAGS_MINFILESIZE with value (1 << 4) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_EOF_FLAGS_PRID with value (1 << 3) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_EOF_FLAGS_SYNC with value (1 << 0) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_EOF_FLAGS_UID with value (1 << 1) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_FSOP_GEOM_FLAGS_FTYPE with value 0x10000 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_FSOP_GEOM_FLAGS_PROJID32 with value 0x0800 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_FSOP_GEOM_FLAGS_V5SB with value 0x8000 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BLFT_BITS with value 5 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BLFT_MASK with value (((1 << XFS_BLFT_BITS) - 1) << XFS_BLFT_SHIFT) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_BLFT_SHIFT with value 11 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_GQUOTA_CHKD with value 0x0100 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_GQUOTA_ENFD with value 0x0080 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_ILOG_AOWNER with value 0x400 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_ILOG_DOWNER with value 0x200 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_LI_ICREATE with value 0x123f has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_MIN_LOG_FACTOR with value 3 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_PQUOTA_CHKD with value 0x0400 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_PQUOTA_ENFD with value 0x0200 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XLOG_REG_TYPE_ICREATE with value 20 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_DQ_FREEING with value 0x0010 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_COMPAT_ALL with value 0 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_COMPAT_UNKNOWN with value ~XFS_SB_FEAT_COMPAT_ALL has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_INCOMPAT_ALL with value (XFS_SB_FEAT_INCOMPAT_FTYPE) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_INCOMPAT_FTYPE with value (1 << 0) has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_INCOMPAT_LOG_ALL with value 0 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_INCOMPAT_LOG_UNKNOWN with value ~XFS_SB_FEAT_INCOMPAT_LOG_ALL has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_INCOMPAT_UNKNOWN with value ~XFS_SB_FEAT_INCOMPAT_ALL has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_RO_COMPAT_ALL with value 0 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_FEAT_RO_COMPAT_UNKNOWN with value ~XFS_SB_FEAT_RO_COMPAT_ALL has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_VERSION2_CRCBIT with value 0x00000100 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_SB_VERSION2_FTYPE with value 0x00000200 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_ICHGTIME_CREATE with value 0x4 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_TRANS_FREEZE_PROT with value 0x40 has been added. | No effect. |
Change | Effect | |
---|---|---|
1 | The constant XFS_TRANS_ICREATE with value 43 has been added. | No effect. |