| Module Name | vmlinux |
|---|---|
| Version #1 | 2.6.33.20 |
| Version #2 | 2.6.34.14 |
| CPU Type | x86_64 |
| Subject | Binary Compatibility |
| Total Header Files | 701 |
|---|---|
| Total Source Files | 1311 |
| Total Objects | 1 |
| Total Symbols / Types | 13860 / 7828 |
| Verdict | Incompatible (47.2%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 323 |
| Removed Symbols | High | 201 |
| Problems with Data Types | High | 42 |
| Medium | 305 | |
| Low | 355 | |
| Problems with Symbols | High | 36 |
| Medium | 451 | |
| Low | 72 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 6 |
| Change | Effect | |
|---|---|---|
| 1 | Field rehash_list 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 max_phys_segments 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 no_cluster 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 ps 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 _removed 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 tx_queue_len 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 wakeup_work 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 cbss 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 capab 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 old_associate_work 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 request 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 work_list 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 force_unicast_rateidx 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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field blacklist 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 get_tx_stats 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 _anon_rss 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 _file_rss 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 anon_vma_node 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 bdata 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 nr_locked 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 transfer 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 alloc_inode 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 free_inode 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 initialize 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. |
| 5 | Field drop 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. |
| 6 | Field free_space 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. |
| 7 | Field alloc_space 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 load_balance 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 move_one_task 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 local_node 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 cb_cis_res 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 cb_cis_virt 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 device_add 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 queue 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. |
| 5 | Field user 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 autoresume 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 autosuspend 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 discon_suspended 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 pm_mutex 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. |
| 5 | Field pm_usage_cnt 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 is_active 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 | 1st middle parameter dname 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 | 3rd middle parameter start 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 | 4th middle parameter len 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 2nd parameter res has been changed from struct resource* (8 bytes) to struct resource const* (8 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter wait has been changed from int (4 bytes) to struct writeback_control* (8 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 2nd parameter wait 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 2nd parameter sync has been changed from int (4 bytes) to struct writeback_control* (8 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 2nd parameter sync 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 | Parameter sb of type struct super_block* 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 4th parameter len has been changed from u64 (8 bytes) to loff_t (8 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| 2 | Type of 3rd parameter start has been changed from u64 (8 bytes) to loff_t (8 bytes). | The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* 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 | Parameter net of type struct net* 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 | 3rd middle parameter p_id 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 | 4th middle parameter pdev_id 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 zone of type u16 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 | Parameter zone of type u16 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 | Parameter zone of type u16 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 | Parameter zone of type u16 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 | Parameter zone of type u16 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 | Parameter zone of type u16 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 | Parameter tmpl of type struct nf_conn* 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 | Parameter net of type struct net* 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 | Parameter net of type struct net* 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 | Parameter net of type struct net* 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 | Parameter net of type struct net* 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 | Parameter band of type enum ieee80211_band 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 | 4th middle parameter orig_requested 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 | 4th middle parameter requested 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 mark of type u32 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 | Parameter mark of type u32 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 | Parameter mark of type struct xfrm_mark* 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 | Parameter mark of type u32 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 | Parameter mark of type u32 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 | Parameter mark of type u32 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 | Parameter mark of type u32 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 | Field parent_package 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 handler_type 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 | Size of field dev has been changed from 336 bytes to 368 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 wakeup has been changed from 120 bytes to 128 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 domain has been changed from 208 bytes to 240 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 api_lock 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 | Size of field dev has been changed from 336 bytes to 368 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 | Field behind_wait 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 cluster 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 cmd has been changed from unsigned char* (8 bytes) to unsigned char[16] (16 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 | The relative position of field q has been changed from 3 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field __data_len has been changed from 8 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field cmd has been changed from 26 to 25. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field cmd_flags has been changed from 4 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field cpu has been changed from 2 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field buffer has been changed from 20 to 21. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field ref_count has been changed from 23 to 19. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | The relative position of field __sector has been changed from 7 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 10 | The relative position of field __cmd has been changed from 25 to 24. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 11 | The relative position of field atomic_flags has been changed from 6 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 12 | The relative position of field cmd_len has been changed from 24 to 26. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 13 | The relative position of field tag has been changed from 21 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field cmd_type has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field errors has been changed from 22 to 23. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field special has been changed from 19 to 20. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field pre_flush_rq has been changed from 336 bytes to 320 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field bar_rq has been changed from 336 bytes to 320 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field post_flush_rq has been changed from 336 bytes to 320 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. |
| 4 | Size of field limits has been changed from 72 bytes to 64 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 ps_timeout 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 | Field len_proberesp_ies 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 beacon_ies 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 proberesp_ies 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 | Field len_beacon_ies 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 action 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 cancel_remain_on_channel 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 remain_on_channel 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 _next_ns_data 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 _vns 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 current_namespace 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 | Field is_radiotap_ns 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. |
| 5 | Field this_arg_size 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. |
| 6 | The relative position of field this_arg_index has been changed from 2 to 4. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr_mask 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 coverage_class 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 n_addresses 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 | Field addresses 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. |
| 5 | Size of field dev has been changed from 336 bytes to 368 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 action_registrations 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 action_registrations_lock 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 ps 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 wext has been changed from 248 bytes to 240 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 top_cgroup has been changed from 216 bytes to 712 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 | Type of field subsys has been changed from struct cgroup_subsys_state*[5] (40 bytes) to struct cgroup_subsys_state*[64] (512 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 cancel_attach 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 subsys has been changed from struct cgroup_subsys_state*[5] (40 bytes) to struct cgroup_subsys_state*[64] (512 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 suspend has been added at the middle position of this structural type. | 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 field dev has been changed from 336 bytes to 368 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 pub has been changed from 64 bytes to 96 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 wiphy has been changed from 512 bytes to 544 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 | Field validate 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 | Size of field power has been changed from 32 bytes to 64 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 | The relative position of field offset has been changed from 2 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field ptr has been changed from 1 to 2. | 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 mem has been changed from 24 bytes to 16 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field kdev has been changed from 336 bytes to 368 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 gem_free_object_unlocked 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 | Size of field kdev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 | Field cardmgr 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 dynids has been changed from 24 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 | Type of field lock has been changed from spinlock_t (4 bytes) to struct mutex (32 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 | Type of field metrics has been changed from u32[13] (52 bytes) to u32[14] (56 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field __pad_to_align_refcnt has been changed from long[2] (16 bytes) to long[1] (8 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 336 bytes to 368 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 | Field i_state_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 i_state has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member FIX_BTMAP_BEGIN has been changed from 2559 to 2438. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member __end_of_fixed_addresses has been changed from 2560 to 2439. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field s_blocksize has been changed from 2 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field s_vfs_rename_mutex has been changed from 36 to 37. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field s_dirt has been changed from 4 to 2. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field s_time_gran has been changed from 37 to 36. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field show_format has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field part0 has been changed from 424 bytes to 456 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 __dev has been changed from 336 bytes to 368 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 self has been changed from 120 bytes to 128 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 nids 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 pins_shutup 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 | Size of field dev has been changed from 336 bytes to 368 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 clock_was_set 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 | Size of field dev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 alert 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 bbaddr 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 flip_pending_is_done 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 saveMCHBAR_RENDER_STANDBY 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 is_gen6 has been added at the middle position of this structural type. | 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 ap_smps 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 req_smps 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 recalc_smps 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 smps_mode 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 sta_finish_work 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 | Field sta_mtx 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. |
| 5 | Field sta_pending_list 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. |
| 6 | Field tmp_channel 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. |
| 7 | Field tmp_channel_type 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. |
| 8 | Field uapsd_max_sp_len 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. |
| 9 | Field uapsd_queues 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. |
| 10 | Field work_list 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. |
| 11 | Field work_mtx 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. |
| 12 | Field work_skb_queue 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. |
| 13 | Field work_timer 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. |
| 14 | Field work_work 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. |
| 15 | Field scan_ps_enabled has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field name 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 rc_rateidx_mask 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 | Size of field u has been changed from 616 bytes to 576 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field wdev has been changed from 504 bytes to 528 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 | Size of field vif has been changed from 48 bytes to 56 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 6 | Field max_ratectrl_rateidx has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mgd has been changed from 616 bytes to 576 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mc_lock has been changed from struct rwlock_t to spinlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu 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 min_ttl has been added at the middle position of this structural type. | Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications. |
| 2 | The relative position of field inet_id has been changed from 11 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field inet_sport has been changed from 10 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field opt has been changed from 9 to 11. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field cnf has been changed from 112 bytes to 120 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 | Type of field data has been changed from int[24] (96 bytes) to int[25] (100 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 dev has been changed from 336 bytes to 368 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 filter 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 match 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 | The relative position of field busy has been changed from 9 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field cursor_addr has been changed from 4 to 13. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field dpms_mode has been changed from 8 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field idle_timer has been changed from 10 to 8. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 5 | The relative position of field lut_g has been changed from 6 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 6 | The relative position of field lut_r has been changed from 5 to 3. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 7 | The relative position of field overlay has been changed from 12 to 10. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field unpin_work has been changed from 13 to 11. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 9 | The relative position of field cursor_bo has been changed from 3 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field lowfreq_avail has been changed from 11 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field lut_b has been changed from 7 to 5. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field last_waited has been changed from 5 to 6. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field nr_batch_requests has been changed from 6 to 5. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fib_metrics has been changed from u32[13] (52 bytes) to u32[14] (56 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 timer_rand_state 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 | Field sff_irq_check 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 sk_list 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 | Field ps_dtim_period has been added at the middle position of this structural type. | 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 sta_add 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 sta_remove 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 rss_stat 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 vm_prev 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 anon_vma_chain 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 | Size of field node_zones has been changed from 9216 bytes to 7168 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 percpu_size 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 nfnl 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 nfnl_stash 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 | Size of field reg_state has been changed from 4 bytes to 2 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field dev has been changed from 336 bytes to 368 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 | Type of field rx_np has been changed from struct netpoll* (8 bytes) to struct list_head (16 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 | Type of field expecting has been changed from u8[3] (3 bytes) to u8[4] (4 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member NF_CT_EXT_NUM has been changed from 4 to 5. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field offset has been changed from u8[4] (4 bytes) to u8[5] (5 bytes). | 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 | Value of member SIP_HDR_CONTENT_LENGTH has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member SIP_HDR_EXPIRES has been changed from 5 to 6. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field ncommit 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 sklist_lock has been changed from struct rwlock_t to spinlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cur_bus_speed 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 max_bus_speed 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 resources 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 dev has been changed from 336 bytes to 368 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 resource has been changed from struct resource*[16] (128 bytes) to struct resource*[4] (32 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 pme_interrupt 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 dev has been changed from 336 bytes to 368 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 cur_bus_speed 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. |
| 2 | Field max_bus_speed 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 | Field get_cur_bus_speed 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. |
| 2 | Field get_max_bus_speed 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 device has been changed from 336 bytes to 368 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 | Field tsleep 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 twake 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 last_tag 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 | Size of field ctx has been changed from 168 bytes to 184 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 output has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field flexible_groups 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 refcount 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 start 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 stop 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 | Size of field dev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 mls_enabled 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 | Value of member POWER_SUPPLY_PROP_CAPACITY has been changed from 29 to 30. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member POWER_SUPPLY_PROP_CAPACITY_LEVEL has been changed from 30 to 31. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member POWER_SUPPLY_PROP_CHARGE_AVG has been changed from 21 to 22. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY has been changed from 19 to 20. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY_DESIGN has been changed from 17 to 18. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL has been changed from 18 to 19. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN has been changed from 16 to 17. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 8 | Value of member POWER_SUPPLY_PROP_CHARGE_NOW has been changed from 20 to 21. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 9 | Value of member POWER_SUPPLY_PROP_CURRENT_AVG has been changed from 13 to 14. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 10 | Value of member POWER_SUPPLY_PROP_CURRENT_NOW has been changed from 12 to 13. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 11 | Value of member POWER_SUPPLY_PROP_ENERGY_AVG has been changed from 28 to 29. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 12 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY has been changed from 26 to 27. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 13 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY_DESIGN has been changed from 24 to 25. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 14 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL has been changed from 25 to 26. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 15 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL_DESIGN has been changed from 23 to 24. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 16 | Value of member POWER_SUPPLY_PROP_ENERGY_NOW has been changed from 27 to 28. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 17 | Value of member POWER_SUPPLY_PROP_MANUFACTURER has been changed from 38 to 39. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 18 | Value of member POWER_SUPPLY_PROP_MODEL_NAME has been changed from 37 to 38. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 19 | Value of member POWER_SUPPLY_PROP_POWER_AVG has been changed from 15 to 16. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 20 | Value of member POWER_SUPPLY_PROP_POWER_NOW has been changed from 14 to 15. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 21 | Value of member POWER_SUPPLY_PROP_SERIAL_NUMBER has been changed from 39 to 40. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 22 | Value of member POWER_SUPPLY_PROP_TEMP has been changed from 31 to 32. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 23 | Value of member POWER_SUPPLY_PROP_TEMP_AMBIENT has been changed from 32 to 33. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 24 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_AVG has been changed from 34 to 35. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 25 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_NOW has been changed from 33 to 34. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 26 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_AVG has been changed from 36 to 37. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 27 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_NOW has been changed from 35 to 36. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 28 | Value of member POWER_SUPPLY_PROP_VOLTAGE_AVG has been changed from 11 to 12. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 29 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MIN has been changed from 7 to 8. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 30 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MIN_DESIGN has been changed from 9 to 10. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 31 | Value of member POWER_SUPPLY_PROP_VOLTAGE_NOW has been changed from 10 to 11. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field claim_space 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. |
| 2 | Field reserve_space 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. |
| 3 | Field release_rsv 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 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fqslock has been changed from spinlock_t to raw_spinlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 2 | Type of field onofflock has been changed from spinlock_t to raw_spinlock_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 3 | Field completed_fqs 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 | Size of field dev has been changed from 336 bytes to 368 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 cpu_power 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 | The relative position of field tk_runstate has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 2 | The relative position of field tk_ops has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field tk_action has been changed from 10 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field tk_callback has been changed from 9 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field tk_waitqueue has been changed from 17 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field tk_timeout has been changed from 13 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field tk_timeouts has been changed from 19 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field tk_calldata has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field tk_priority has been changed from 24 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field tk_bytes_sent has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field tk_flags has been changed from 14 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field tk_owner has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field u has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field tk_rebind_retry has been changed from 25 to 9. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field tk_rtt has been changed from 22 to 23. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field tk_start has been changed from 21 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field tk_workqueue has been changed from 16 to 17. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field moved_group 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 | Field span_weight 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 rss_stat has been added at the middle position of this structural type. | 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 ptrace_bp_refcnt has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field bio_tail 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 | Type of field epoll_watches has been changed from struct atomic_t (4 bytes) to atomic_long_t (8 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field sdev_dev has been changed from 336 bytes to 368 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 sdev_gendev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 shost_dev has been changed from 336 bytes to 368 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 shost_gendev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 port has been changed from 200 bytes to 208 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 dev has been changed from 336 bytes to 368 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 | Field registered 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 | The relative position of field offset has been changed from 3 to 4. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field flags has been changed from 0 to 1. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 3 | The relative position of field cpu_slab has been changed from 18 to 0. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 4 | The relative position of field objsize has been changed from 2 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field oo has been changed from 4 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field size has been changed from 1 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[75] (600 bytes) to unsigned long[77] (616 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field limit has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dead has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field device_add_pending has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field mfc_pfc has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field present 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 | Field ops_mutex 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 dev has been changed from 336 bytes to 368 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 | Field lock 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 | Field attrs 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 | The relative position of field s_mode has been changed from 8 to 7. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 2 | The relative position of field s_ino has been changed from 7 to 8. | 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 nonagle has been changed from 1 byte to 4 bits. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field device has been changed from 336 bytes to 368 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 device has been changed from 336 bytes to 368 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 console 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 get_icount 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 dcd_change 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 hs_companion 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 | Size of field dev has been changed from 336 bytes to 368 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 | Field skip_sys_resume has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 336 bytes to 368 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 dev has been changed from 336 bytes to 368 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 | Field wb_start 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 net 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 priority has been added at the middle position of this structural type. | 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 net 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 mark 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 mark 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 | Size of this global data has been changed from 40 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter props of type struct backlight_properties const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter b became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter t became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bdev became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter disk became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter offset became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 384 bytes to 408 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter count of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter css became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter id became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ss became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter css became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ss became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4456 bytes to 4952 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 208 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4456 bytes to 4952 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 208 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4456 bytes to 4952 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 208 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4456 bytes to 4952 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 208 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 4456 bytes to 4952 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 208 bytes to 224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter s became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter from_file of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cmd became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter number has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter number has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter type has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wait of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 360 bytes to 376 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter type has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type u8 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter gpe_device became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter gpe_number became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type u8 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter gpe_device became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter gpe_number became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hid became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hid became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hid became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter align became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter data became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter res became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter size became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from spinlock_t to raw_spinlock_t of different format. | This global data may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp of type gfp_t has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter dev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter begin became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter end became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter what became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output (976 bytes) to struct intel_encoder (1008 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output (976 bytes) to struct intel_encoder (1008 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output (976 bytes) to struct intel_encoder (1008 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output (976 bytes) to struct intel_encoder (1008 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output (976 bytes) to struct intel_encoder (1008 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output (976 bytes) to struct intel_encoder (1008 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter gsi became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fieinfo became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter get_block became passed in r8 register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter inode became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter len became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 5 | The parameter start became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pagenr became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter hflag of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 456 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 456 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 456 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 456 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 456 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 456 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 456 bytes to 464 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rwlock_t to spinlock_t of different format. | This global data may be incorrectly accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter da became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sa became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter skb became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter desc became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter irq became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter resume became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Any attempts of old applications to change this global data may result in crash. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 384 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 704 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 720 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 720 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 384 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 704 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 360 bytes to 376 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 128 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 504 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 248 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 512 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 168 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 1472 bytes to 1536 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 384 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 720 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 704 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 360 bytes to 376 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 128 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 504 bytes to 528 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 248 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 512 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 168 bytes to 200 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 384 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 704 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 720 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 1472 bytes to 1536 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 600 bytes to 616 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 384 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 704 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 720 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 2152 bytes to 2168 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 112 bytes to 120 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 384 bytes to 392 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 184 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 704 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 720 bytes to 728 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hooknum became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter net became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter pf became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter skb became passed in rcx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter secs of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter node became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter pxm became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter cpu has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cpu has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter cpu has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cpu has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter regs of type struct pt_regs* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 440 bytes to 472 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter from_file of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bus became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter devfn became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter vns of type struct ieee80211_radiotap_vendor_namespaces const* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter iterator became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter max_length became passed in rdx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 4 | The parameter radiotap_header became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter irq_flags of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter alpha2 became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nla_policy[21] const (84 bytes) to struct nla_policy[23] const (92 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 84 bytes to 92 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bss became passed in rsi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter local became passed in rdi register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter cpu became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sd became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 176 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 176 bytes to 184 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 336 bytes to 320 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 424 bytes to 456 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 32 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 2272 bytes to 2216 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 336 bytes to 368 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 728 bytes to 712 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 592 bytes to 624 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 144 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 72 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 824 bytes to 832 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of return value has been decreased from 1 to 0. | Applications may try to access unallocated memory by the dereferencing of new return value and therefore cause a crash. |
| 2 | Parameter buf of type unsigned char* has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 3 | Parameter buf_len of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 4 | Type of return value has been changed from unsigned char* (8 bytes) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter from_file of type bool has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Applications will not obtain a return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 432 bytes to 440 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter object became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter s became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct kmem_cache[14] (17696 bytes) to struct kmem_cache[28] (19488 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 17696 bytes to 19488 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter local has been changed from struct ieee80211_local (3456 bytes) to struct ieee80211_sub_if_data (1592 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter len became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter s1 became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter s2 became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter name has been changed from struct new_utsname (390 bytes) to struct old_utsname (325 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int[3] (12 bytes) to long[3] (24 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 12 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct atomic_t (4 bytes) to atomic_long_t (8 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 1264 bytes to 696 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 56 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter init_rcv_wnd of type __u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter event_call became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 80 bytes to 72 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 536 bytes to 544 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int[3] (12 bytes) to long[3] (24 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 12 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct atomic_t (4 bytes) to atomic_long_t (8 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 6960 bytes to 7008 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter base became passed on stack instead of rdx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter cp became passed on stack instead of rdi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter endp became passed on stack instead of rsi register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 176 bytes to 208 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from short (2 bytes) to int (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Field runtime_count has been added to this type. | This field will not be initialized by old clients. 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 wakeup_count has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 32 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field integer has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Field integer64 has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field value has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field next 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 40 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field notify has been changed from 40 bytes to 56 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1184 bytes to 1224 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field run_wake_count 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 120 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field gpe_number has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field sleep_state has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field always_enabled has been added to this type. | This field will not be initialized by old clients. 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 notifier_present has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field address has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field value has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from acpi_status(*)(u32, acpi_physical_address, u32, acpi_integer*, void*, void*) to acpi_status(*)(u32, acpi_physical_address, u32, u64*, void*, void*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 504 bytes to 536 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 208 bytes to 240 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 168 bytes to 152 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 456 bytes to 488 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 check_fb has been changed from int(*)(struct fb_info*) to int(*)(struct backlight_device*, struct fb_info*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field get_brightness has been changed from int(*)(struct backlight_device*) const to int(*)(struct backlight_device*). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field options has been changed from unsigned int const to unsigned int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field update_status has been changed from int(*)(struct backlight_device*) const to int(*)(struct backlight_device*). | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 224 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 | Size of this type has been changed from 72 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field max_hw_segments has been renamed to max_segments. | 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 336 bytes to 320 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field cmd has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2272 bytes to 2216 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 248 bytes to 240 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 64 bytes to 96 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 384 bytes to 408 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field _reset_on_ext 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 56 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field arg has been changed from u8* to unsigned char*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field bitmap_shifter has been changed from u32 to uint32_t. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field next_bitmap has been changed from __le32* to uint32_t*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field this_arg has been changed from u8* to unsigned char*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 512 bytes to 544 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 504 bytes to 528 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field ps_timeout has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 4456 bytes to 4952 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field register_event 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 unregister_event 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 176 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field event_list 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 event_list_lock 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 216 bytes to 712 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field module 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 208 bytes to 224 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 112 bytes to 584 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 4 has been changed from USB_SPEED_VARIABLE to USB_SPEED_WIRELESS. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Field retries 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 120 bytes to 128 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 resume has been changed from void(*)() to void(*)(struct clocksource*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 656 bytes to 688 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 128 bytes to 160 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field proberesp_ies_allocated has been added to this type. | This field will not be initialized by old clients. 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 ies_allocated has been renamed to beacon_ies_allocated. | 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 896 bytes to 928 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 40 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field requery has been changed from void(*)(struct pcmcia_socket*, int) to void(*)(struct pcmcia_socket*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field show has been changed from ssize_t(*)(struct class*, char*) to ssize_t(*)(struct class*, struct class_attribute*, char*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field store has been changed from ssize_t(*)(struct class*, char const*, size_t) to ssize_t(*)(struct class*, struct class_attribute*, char const*, size_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 336 bytes to 368 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 16 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 48 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 848 bytes to 880 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 848 bytes to 856 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 504 bytes to 536 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 544 bytes to 568 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field reserved has been changed from 3 bits to 4 bits. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 176 bytes to 200 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 48 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 1744 bytes to 1736 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 352 bytes to 384 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_rx_ntuple 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 set_rx_ntuple 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 360 bytes to 376 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field commit_metadata 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 40 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 | Size of this type has been changed from 824 bytes to 832 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member FIX_BTMAP_END has been changed from 2304 to 2183. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 728 bytes to 712 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 write_inode has been changed from int(*)(struct inode*, int) to int(*)(struct inode*, struct writeback_control*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field print_fmt has been added to this type. | This field will not be initialized by old clients. 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 profile_count has been renamed to perf_refcount. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field profile_disable has been renamed to perf_event_disable. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 4 | Field profile_enable has been renamed to perf_event_enable. | 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 592 bytes to 624 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 424 bytes to 456 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset_device 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 256 bytes to 264 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 408 bytes to 384 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 776 bytes to 800 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 7072 bytes to 7104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field hid_output_raw_report has been changed from int(*)(struct hid_device*, __u8*, size_t) to int(*)(struct hid_device*, __u8*, size_t, unsigned char). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 184 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field userspace_clients 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 512 bytes to 560 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 400 bytes to 432 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 216 bytes to 224 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_bo 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 active_bo_count 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 batchbuffer 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 ringbuffer 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 | Size of this type has been changed from 64 bytes to 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field compressed_fb 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 compressed_llb 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 cur_delay 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 max_delay 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 mchbar_need_disable 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 min_delay 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 no_fbc_reason 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 | Size of this type has been changed from 4560 bytes to 4592 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 9 | Field lvds_edid_good has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_smps has been added to this type. | NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field uapsd_supported has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 616 bytes to 576 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field associated has been changed from struct ieee80211_bss (168 bytes) to struct cfg80211_bss (96 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 3456 bytes to 3776 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field offchannel_ps_enabled has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1584 bytes to 1592 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 64 bytes to 56 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 616 bytes to 576 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu 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 32 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 | Size of this type has been changed from 8 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 384 bytes to 392 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 112 bytes to 120 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 2456 bytes to 2488 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field getkeycode has been changed from int(*)(struct input_dev*, int, int*) to int(*)(struct input_dev*, unsigned int, unsigned int*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field setkeycode has been changed from int(*)(struct input_dev*, int, int) to int(*)(struct input_dev*, unsigned int, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 112 bytes to 120 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cursor_height 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 cursor_width 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 cursor_x 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 cursor_y 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 | Size of this type has been changed from 1232 bytes to 1240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 6 | Field cursor_visble has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 72 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 128 bytes to 136 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field initialized has been renamed to state. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysfs_ops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field sysfs_ops has been changed from struct sysfs_ops* to struct sysfs_ops const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field uevent_ops became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field uevent_ops has been changed from struct kset_uevent_ops* to struct kset_uevent_ops const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Added const qualifier to field name. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Field uevent became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Field filter became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 4 | Type of field uevent has been changed from int(*)(struct kset*, struct kobject*, struct kobj_uevent_env*) to int(*)(struct kset*, struct kobject*, struct kobj_uevent_env*) const. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field filter has been changed from int(*)(struct kset*, struct kobject*) to int(*)(struct kset*, struct kobject*) const. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field name has been changed from char const*(*)(struct kset*, struct kobject*) to char const*(*)(struct kset*, struct kobject*) const. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 456 bytes to 464 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_count 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 sk_dev_hash 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 sk_laddr_hash 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 sk_lock 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 | Size of this type has been changed from 56 bytes to 1072 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field smps_mode has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush 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 set_coverage_class 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 216 bytes to 240 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 4 | Base type of field add_interface has been changed from int(*)(struct ieee80211_hw*, struct ieee80211_if_init_conf*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 5 | Base type of field remove_interface has been changed from void(*)(struct ieee80211_hw*, struct ieee80211_if_init_conf*) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 6 | Base type of field update_tkip_key has been changed from void(*)(struct ieee80211_hw*, struct ieee80211_key_conf*, u8 const*, u32, u16*) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct ieee80211_key_conf*, struct ieee80211_sta*, u32, u16*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rate_idx_mask 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 40 bytes to 48 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field ap has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr 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 48 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysfs_active has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field hugetlb_entry has been changed from int(*)(pte_t*, unsigned long, unsigned long, struct mm_walk*) to int(*)(pte_t*, unsigned long, unsigned long, unsigned long, struct mm_walk*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 824 bytes to 832 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 176 bytes to 184 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 18688 bytes to 16640 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 2304 bytes to 1792 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field pageset has been changed from struct per_cpu_pageset* (8 bytes) to struct per_cpu_pageset (96 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | Field all_unreclaimable has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | The pointer level of field pageset has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 536 bytes to 544 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field refptr has been changed from char (1 byte) to struct module_ref (8 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 2152 bytes to 2168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ethtool_ntuple_list 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 1472 bytes to 1536 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field rtnl_link_state has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_get_vf_config 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 ndo_set_vf_mac 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 ndo_set_vf_tx_rate 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 ndo_set_vf_vlan 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 | Size of this type has been changed from 168 bytes to 200 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx 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 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 184 bytes to 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | The pointer level of field rx_np has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field name 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 16 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 error has been changed from int(*)(struct net*, struct sk_buff*, unsigned int, enum ip_conntrack_info*, u_int8_t, unsigned int) to int(*)(struct net*, struct nf_conn*, struct sk_buff*, unsigned int, enum ip_conntrack_info*, u_int8_t, unsigned int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 4 has been changed from SIP_HDR_VIA to SIP_HDR_VIA_UDP. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1040 bytes to 1048 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 656 bytes to 616 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 1472 bytes to 1504 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field run_wake 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 40 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 | Size of this type has been changed from 12 bytes to 4 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 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 368 bytes to 400 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 856 bytes to 888 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_hw_ptr_interrupt has been renamed to prev_hw_ptr_period. | 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 32 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field last_cpu has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 208 bytes to 224 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attach_state has been added to this type. | This field will not be initialized by old clients. 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 group_flags has been added to this type. | This field will not be initialized by old clients. 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 mmap_locked has been added to this type. | This field will not be initialized by old clients. 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 mmap_user has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 168 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field group_list has been renamed to pinned_groups. | 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 96 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 32 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 info has been added to this type. | 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 unnamed2 has been removed from this union. | Applications may access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 720 bytes to 752 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 632 bytes to 664 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 376 bytes to 408 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field id_entry became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 3 | Type of field id_entry has been changed from struct platform_device_id* to struct platform_device_id const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field id_table became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Type of field id_table has been changed from struct platform_device_id* to struct platform_device_id const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field completion 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 32 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field async_suspend has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 480 bytes to 512 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 576 bytes to 608 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 440 bytes to 472 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 432 bytes to 440 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field range_tr has been changed from struct range_trans (72 bytes) to struct hashtab (32 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member POWER_SUPPLY_PROP_CHARGE_COUNTER has been changed from 22 to 23. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MAX has been changed from 6 to 7. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MAX_DESIGN has been changed from 8 to 9. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field bus_master_latency has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field control has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field core_frequency has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field power has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field status has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field transition_latency has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field control has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field freqpercentage has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field power has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field status has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field transition_latency has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field coord_type has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field domain has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field num_entries has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field num_processors has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field revision has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field coord_type has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field domain has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field num_entries has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field num_processors has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field revision has been changed from acpi_integer to u64. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ignore_parity has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 144 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 | Base type of field quota_sync has been changed from int(*)(struct super_block*, int) to int(*)(struct super_block*, int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field completed has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field gpnum has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field n_rcu_pending has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field n_rp_cb_ready has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field n_rp_cpu_needs_gp has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field n_rp_gp_completed has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field n_rp_gp_started has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 8 | Type of field n_rp_need_fqs has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 9 | Type of field n_rp_need_nothing has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 10 | Type of field n_rp_qs_pending has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 11 | Type of field passed_quiesc_completed has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field completed has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field gpnum has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field fqs_active has been added to this type. | This field will not be initialized by old clients. 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 fqs_need_gp has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 3 | Type of field completed has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field gpnum has been changed from long to unsigned long. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field syn_ack_timeout 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 56 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 592 bytes to 624 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 2408 bytes to 2416 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field task_move_group 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 200 bytes to 184 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Base type of field enqueue_task has been changed from void(*)(struct rq*, struct task_struct*, int) to void(*)(struct rq*, struct task_struct*, int, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 4 | Base type of field select_task_rq has been changed from int(*)(struct task_struct*, int, int) to int(*)(struct rq*, struct task_struct*, int, int). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 256 bytes to 264 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 bio_list has been changed from struct bio (104 bytes) to struct bio_list (16 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 1032 bytes to 1096 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 464 bytes to 496 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 1088 bytes to 1152 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 392 bytes to 424 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 syslog has been changed from int(*)(int) to int(*)(int, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 272 bytes to 280 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 544 bytes to 576 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 1264 bytes to 696 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field cpu_slab has been changed from struct kmem_cache_cpu* (8 bytes) to struct kmem_cache_cpu (24 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 3 | The pointer level of field cpu_slab has been decreased from 1 to 0. | The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 600 bytes to 616 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 sysctl_mem has been changed from int (4 bytes) to long (8 bytes). | Possible access of applications to incorrect memory through the pointer. |
| 2 | Base type of field memory_allocated has been changed from struct atomic_t (4 bytes) to struct atomic64_t (8 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_pfc has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field suspended_state 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 960 bytes to 944 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field present has been added to this type. | This field will not be initialized by old clients. 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 sysfs_events has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pin_status has been renamed to uploaded. | 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 144 bytes to 152 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 show has been changed from ssize_t(*)(struct sysdev_class*, char*) to ssize_t(*)(struct sysdev_class*, struct sysdev_class_attribute*, char*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field store has been changed from ssize_t(*)(struct sysdev_class*, char const*, size_t) to ssize_t(*)(struct sysdev_class*, struct sysdev_class_attribute*, char const*, size_t). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 72 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field s_mode has been changed from umode_t to unsigned short. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field thin_dupack has been added to this type. | This field will not be initialized by old clients. 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 thin_lto has been added to this type. | This field will not be initialized by old clients. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 392 bytes to 424 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 616 bytes to 648 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 200 bytes to 208 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 240 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 | Size of this type has been changed from 144 bytes to 152 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 120 bytes to 128 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 1352 bytes to 1200 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 432 bytes to 464 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 352 bytes to 384 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 72 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 | Field pci 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 176 bytes to 208 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nmi_init 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 40 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 | Base type of field compat_from_user has been changed from void(*)(void*, void*) to void(*)(void*, void const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field compat_to_user has been changed from int(*)(void*, void*) to int(*)(void*, void const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 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 | Base type of field compat_from_user has been changed from void(*)(void*, void*) to void(*)(void*, void const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field compat_to_user has been changed from int(*)(void*, void*) to int(*)(void*, void const*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 40 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 | Size of this type has been changed from 720 bytes to 728 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 704 bytes to 712 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mode has been changed from __u8 to u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field optional has been changed from __u8 to u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 3 | Type of field reqid has been changed from __u32 to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field share has been changed from __u8 to u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 5 | Type of field allalgs has been changed from __u8 to u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 6 | Type of field aalgos has been changed from __u32 to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 7 | Type of field ealgos has been changed from __u32 to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 8 | Type of field calgos has been changed from __u32 to u32. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field err_handler has been changed from int(*)(struct sk_buff*, __u32) to int(*)(struct sk_buff*, u32). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field flags has been changed from __u8 to u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 2 | Type of field proto has been changed from __u8 to u8. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter max_sectors has been renamed to max_hw_sectors. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter offset has been renamed to start. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 7th parameter alignf has been changed from void(*)(void*, struct resource*, resource_size_t, resource_size_t) to resource_size_t(*)(void*, struct resource const*, resource_size_t, resource_size_t). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter end has been changed from size_t to resource_size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter start has been changed from size_t to resource_size_t. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 5th parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter field_value has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter mask has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter integer0 has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter integer1 has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter integer0 has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter integer1 has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of return value has been changed from acpi_integer to u64. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter how_long has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter compressed_id has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter value has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter address has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to resource_size_t (8 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct icmp_err[] to struct icmp_err[] const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter wait has been renamed to wbc. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter sync has been renamed to wbc. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter scancode has been changed from int to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Base type of 3rd parameter keycode has been changed from int to unsigned int. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter keycode has been changed from int to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter scancode has been changed from int to unsigned int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter output_device has been renamed to sdvo_reg. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pagenr has been renamed to pfn. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct sysfs_ops to struct sysfs_ops const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter uevent_ops has been changed from struct kset_uevent_ops* to struct kset_uevent_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter ops has been changed from struct mtrr_ops* to struct mtrr_ops const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct mtrr_ops to struct mtrr_ops const. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct mtrr_ops* to struct mtrr_ops const*. | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int, unsigned int*, enum sdp_header_types, enum sdp_header_types, union nf_inet_addr const*) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, enum sdp_header_types, enum sdp_header_types, union nf_inet_addr const*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int*, struct nf_conntrack_expect*, struct nf_conntrack_expect*, unsigned int, unsigned int, union nf_inet_addr*) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, struct nf_conntrack_expect*, unsigned int, unsigned int, union nf_inet_addr*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int*, unsigned int, unsigned int, u_int16_t) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, unsigned int, u_int16_t). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int, unsigned int*, union nf_inet_addr const*) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, union nf_inet_addr const*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int*, struct nf_conntrack_expect*, unsigned int, unsigned int) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, unsigned int, unsigned int). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int*) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*). | Replacement of data type may indicate a change in semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter ms has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter value has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter group_leader has been renamed to leader. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 7th parameter alignf has been changed from void(*)(void*, struct resource*, resource_size_t, resource_size_t) to resource_size_t(*)(void*, struct resource const*, resource_size_t, resource_size_t). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter arg has been changed from struct mmap_arg_struct to struct mmap_arg_struct32. | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter value has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter integer has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter addr has been changed from u8* to u8 const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter in_dividend has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 2nd parameter in_divisor has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 3 | Type of 3rd parameter out_quotient has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 4 | Type of 4th parameter out_remainder has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter in_dividend has been changed from acpi_integer to u64. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter out_quotient has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter ret_integer has been changed from acpi_integer* to u64*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter m has been changed from struct xt_entry_match* to struct xt_entry_match const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter t has been changed from struct xt_entry_target* to struct xt_entry_target const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_brightness became non-const. | No effect. |
| 2 | Field options became non-const. | No effect. |
| 3 | Field update_status became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NF_CT_EXT_ZONE with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SIP_HDR_VIA_TCP with value 5 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_PROP_CYCLE_COUNT with value 6 has been added. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 2.6.33.20 |
| Version #2 | 2.6.34.14 |
| CPU Type | x86_64 |
| Subject | Source Compatibility |
| Total Header Files | 701 |
|---|---|
| Total Source Files | 1311 |
| Total Objects | 1 |
| Total Symbols / Types | 13870 / 7830 |
| Verdict | Incompatible (52.5%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 327 |
| Removed Symbols | High | 201 |
| Problems with Data Types | High | 85 |
| Medium | 20 | |
| Low | 245 | |
| Problems with Symbols | High | 29 |
| Medium | 44 | |
| Low | 38 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 111 |
| Other Changes in Symbols | - | 17 |
| Change | Effect | |
|---|---|---|
| 1 | Field integer64 has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rehash_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct autofs_info' has no member named 'rehash_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field alarm_present has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_battery' has no member named 'alarm_present'. |
| 2 | Field quirks has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_battery' has no member named 'quirks'. |
| Change | Effect | |
|---|---|---|
| 1 | Field no_cluster has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct queue_limits' has no member named 'no_cluster'. |
| 2 | Field max_phys_segments has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct queue_limits' has no member named 'max_phys_segments'. |
| 3 | Field max_hw_segments has been renamed to max_segments. | Recompilation of a client program may be broken with the error message: struct queue_limits has no member named max_hw_segments. |
| Change | Effect | |
|---|---|---|
| 1 | Field ps_timeout has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-cfg80211.h-1441' has no member named 'ps_timeout'. |
| 2 | Field ps has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-cfg80211.h-1441' has no member named 'ps'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 4 has been changed from USB_SPEED_VARIABLE to USB_SPEED_WIRELESS. | Recompilation of a client program may be broken with the error message: 'USB_SPEED_VARIABLE' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field ies_allocated has been renamed to beacon_ies_allocated. | Recompilation of a client program may be broken with the error message: struct cfg80211_internal_bss has no member named ies_allocated. |
| Change | Effect | |
|---|---|---|
| 1 | Field _removed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_device' has no member named '_removed'. |
| 2 | Field cardmgr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_device' has no member named 'cardmgr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field tx_queue_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct e1000_adapter' has no member named 'tx_queue_len'. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext3_inode_info' has no member named 'i_state'. |
| Change | Effect | |
|---|---|---|
| 1 | Field show_format has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ftrace_event_call' has no member named 'show_format'. |
| 2 | Field profile_count has been renamed to perf_refcount. | Recompilation of a client program may be broken with the error message: struct ftrace_event_call has no member named profile_count. |
| 3 | Field profile_disable has been renamed to perf_event_disable. | Recompilation of a client program may be broken with the error message: struct ftrace_event_call has no member named profile_disable. |
| 4 | Field profile_enable has been renamed to perf_event_enable. | Recompilation of a client program may be broken with the error message: struct ftrace_event_call has no member named profile_enable. |
| Change | Effect | |
|---|---|---|
| 1 | Field wakeup_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_hcd' has no member named 'wakeup_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cbss has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss' has no member named 'cbss'. |
| Change | Effect | |
|---|---|---|
| 1 | Field capab has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_managed' has no member named 'capab'. |
| 2 | Field old_associate_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_managed' has no member named 'old_associate_work'. |
| 3 | Field request has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_managed' has no member named 'request'. |
| 4 | Field work_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_managed' has no member named 'work_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field scan_ps_enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_local' has no member named 'scan_ps_enabled'. |
| Change | Effect | |
|---|---|---|
| 1 | Field force_unicast_rateidx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_sub_if_data' has no member named 'force_unicast_rateidx'. |
| 2 | Field max_ratectrl_rateidx has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_sub_if_data' has no member named 'max_ratectrl_rateidx'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_tx_data' has no member named 'dev'. |
| Change | Effect | |
|---|---|---|
| 1 | Field blacklist has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct input_handler' has no member named 'blacklist'. |
| Change | Effect | |
|---|---|---|
| 1 | Field timer_rand_state has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct irq_desc' has no member named 'timer_rand_state'. |
| Change | Effect | |
|---|---|---|
| 1 | Field initialized has been renamed to state. | Recompilation of a client program may be broken with the error message: struct tkip_ctx has no member named initialized. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct llc_sap' has no member named 'sk_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_tx_stats has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_ops' has no member named 'get_tx_stats'. |
| Change | Effect | |
|---|---|---|
| 1 | Field _file_rss has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named '_file_rss'. |
| 2 | Field _anon_rss has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mm_struct' has no member named '_anon_rss'. |
| Change | Effect | |
|---|---|---|
| 1 | Field anon_vma_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct vm_area_struct' has no member named 'anon_vma_node'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bdata has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pglist_data' has no member named 'bdata'. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 4 has been changed from SIP_HDR_VIA to SIP_HDR_VIA_UDP. | Recompilation of a client program may be broken with the error message: 'SIP_HDR_VIA' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field cur_bus_speed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hotplug_slot_info' has no member named 'cur_bus_speed'. |
| 2 | Field max_bus_speed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hotplug_slot_info' has no member named 'max_bus_speed'. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_cur_bus_speed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hotplug_slot_ops' has no member named 'get_cur_bus_speed'. |
| 2 | Field get_max_bus_speed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hotplug_slot_ops' has no member named 'get_max_bus_speed'. |
| Change | Effect | |
|---|---|---|
| 1 | Field prev_hw_ptr_interrupt has been renamed to prev_hw_ptr_period. | Recompilation of a client program may be broken with the error message: struct snd_pcm_oss_runtime has no member named prev_hw_ptr_interrupt. |
| Change | Effect | |
|---|---|---|
| 1 | Field output has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_event' has no member named 'output'. |
| Change | Effect | |
|---|---|---|
| 1 | Field group_list has been renamed to pinned_groups. | Recompilation of a client program may be broken with the error message: struct perf_event_context has no member named group_list. |
| Change | Effect | |
|---|---|---|
| 1 | Field nr_locked has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct perf_mmap_data' has no member named 'nr_locked'. |
| Change | Effect | |
|---|---|---|
| 1 | Field unnamed2 has been removed from this union. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field release_rsv has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'release_rsv'. |
| 2 | Field alloc_inode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'alloc_inode'. |
| 3 | Field claim_space has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'claim_space'. |
| 4 | Field initialize has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'initialize'. |
| 5 | Field free_inode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'free_inode'. |
| 6 | Field drop has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'drop'. |
| 7 | Field reserve_space has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'reserve_space'. |
| 8 | Field alloc_space has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'alloc_space'. |
| 9 | Field transfer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'transfer'. |
| 10 | Field free_space has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dquot_operations' has no member named 'free_space'. |
| Change | Effect | |
|---|---|---|
| 1 | Field completed_fqs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_state' has no member named 'completed_fqs'. |
| Change | Effect | |
|---|---|---|
| 1 | Field move_one_task has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_class' has no member named 'move_one_task'. |
| 2 | Field load_balance has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_class' has no member named 'load_balance'. |
| 3 | Field moved_group has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sched_class' has no member named 'moved_group'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bio_tail has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct task_struct' has no member named 'bio_tail'. |
| 2 | Field ptrace_bp_refcnt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct task_struct' has no member named 'ptrace_bp_refcnt'. |
| Change | Effect | |
|---|---|---|
| 1 | Field registered has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct serio' has no member named 'registered'. |
| Change | Effect | |
|---|---|---|
| 1 | Field local_node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kmem_cache' has no member named 'local_node'. |
| Change | Effect | |
|---|---|---|
| 1 | Field limit has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-sock.h-253' has no member named 'limit'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dead has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-ss.h-221' has no member named 'dead'. |
| 2 | Field device_add_pending has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-ss.h-221' has no member named 'device_add_pending'. |
| 3 | Field mfc_pfc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-ss.h-221' has no member named 'mfc_pfc'. |
| 4 | Field present has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-ss.h-221' has no member named 'present'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cb_cis_res has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'cb_cis_res'. |
| 2 | Field cb_cis_virt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'cb_cis_virt'. |
| 3 | Field device_add has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'device_add'. |
| 4 | Field lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'lock'. |
| 5 | Field queue has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'queue'. |
| 6 | Field user has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pcmcia_socket' has no member named 'user'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pin_status has been renamed to uploaded. | Recompilation of a client program may be broken with the error message: struct sta_info has no member named pin_status. |
| Change | Effect | |
|---|---|---|
| 1 | Field autoresume has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'autoresume'. |
| 2 | Field autosuspend has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'autosuspend'. |
| 3 | Field discon_suspended has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'discon_suspended'. |
| 4 | Field pm_mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'pm_mutex'. |
| 5 | Field pm_usage_cnt has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'pm_usage_cnt'. |
| 6 | Field skip_sys_resume has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_device' has no member named 'skip_sys_resume'. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_active has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct usb_interface' has no member named 'is_active'. |
| Change | Effect | |
|---|---|---|
| 1 | 1st middle parameter dname has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter start has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 4th middle parameter len has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter sb of type struct super_block* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter p_id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 4th middle parameter pdev_id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type u16 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type u16 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type u16 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type u16 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type u16 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter zone of type u16 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tmpl of type struct nf_conn* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter net of type struct net* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter band of type enum ieee80211_band has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th middle parameter orig_requested has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th middle parameter requested has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type struct xfrm_mark* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter mark of type u32 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field cmd has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to struct mutex of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field associated has been changed from struct ieee80211_bss to struct cfg80211_bss of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mc_lock has been changed from struct rwlock_t to spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysfs_ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct kobj_type::sysfs_ops'. |
| Change | Effect | |
|---|---|---|
| 1 | Field uevent_ops became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct kset::uevent_ops'. |
| Change | Effect | |
|---|---|---|
| 1 | Field uevent became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct kset_uevent_ops::uevent'. |
| 2 | Field filter became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct kset_uevent_ops::filter'. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field pageset has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field refptr has been changed from char to struct module_ref of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field rx_np has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field sklist_lock has been changed from struct rwlock_t to spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field id_entry became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct platform_device::id_entry'. |
| Change | Effect | |
|---|---|---|
| 1 | Field id_table became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct platform_driver::id_table'. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field range_tr has been changed from struct range_trans to struct hashtab of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field lock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fqslock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field onofflock has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field bio_list has been changed from struct bio to struct bio_list of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field cpu_slab has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter props of type struct backlight_properties const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter count of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter from_file of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter number has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter number has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter wait of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter type has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type u8 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type u8 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from spinlock_t to raw_spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gfp of type gfp_t has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 5th parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter wait has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter sync has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter hflag of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct rwlock_t to spinlock_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | This global data became const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter secs of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter cpu has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cpu has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter cpu has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter cpu has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter regs of type struct pt_regs* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter from_file of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter vns of type struct ieee80211_radiotap_vendor_namespaces const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter irq_flags of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter buf of type unsigned char* has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter buf_len of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| 3 | The pointer level of return value has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter from_file of type bool has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int (4 bytes) to void. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter local has been changed from struct ieee80211_local to struct ieee80211_sub_if_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter name has been changed from struct new_utsname to struct old_utsname of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter init_rcv_wnd of type __u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field runtime_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field wakeup_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field parent_package has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field handler_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field next has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field run_wake_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field always_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field notifier_present has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from acpi_status(*)(u32, acpi_physical_address, u32, acpi_integer*, void*, void*) to acpi_status(*)(u32, acpi_physical_address, u32, u64*, void*, void*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field api_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field check_fb has been changed from int(*)(struct fb_info*) to int(*)(struct backlight_device*, struct fb_info*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cycle_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field max_averaging_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field max_sampling_time has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field measurement_accuracy has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field min_averaging_interval has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field min_sampling_time has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field behind_wait has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cluster has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field cmd has been changed from unsigned char* to unsigned char[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field len_proberesp_ies has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field beacon_ies has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field proberesp_ies has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field len_beacon_ies has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field action has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cancel_remain_on_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field remain_on_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field _next_ns_data has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field _reset_on_ext has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field _vns has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field current_namespace has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field is_radiotap_ns has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field this_arg_size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field addresses has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field coverage_class has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field addr_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field n_addresses has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field action_registrations_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ps_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field action_registrations has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ps has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field register_event has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field unregister_event has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field event_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field event_list_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field subsys has been changed from struct cgroup_subsys_state*[5] to struct cgroup_subsys_state*[64]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field cancel_attach has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field module has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field subsys has been changed from struct cgroup_subsys_state*[5] to struct cgroup_subsys_state*[64]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field retries has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field suspend has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field resume has been changed from void(*)() to void(*)(struct clocksource*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field proberesp_ies_allocated has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field validate has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field requery has been changed from void(*)(struct pcmcia_socket*, int) to void(*)(struct pcmcia_socket*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field show has been changed from ssize_t(*)(struct class*, char*) to ssize_t(*)(struct class*, struct class_attribute*, char*). | Recompilation of a client program may be broken. |
| 2 | Base type of field store has been changed from ssize_t(*)(struct class*, char const*, size_t) to ssize_t(*)(struct class*, struct class_attribute*, char const*, size_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field gem_free_object_unlocked has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field metrics has been changed from u32[13] to u32[14]. | Recompilation of a client program may be broken. |
| 2 | Type of field __pad_to_align_refcnt has been changed from long[2] to long[1]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_rx_ntuple has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field set_rx_ntuple has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field commit_metadata has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field i_state_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field write_inode has been changed from int(*)(struct inode*, int) to int(*)(struct inode*, struct writeback_control*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field print_fmt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field reset_device has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nids has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pins_shutup has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field hid_output_raw_report has been changed from int(*)(struct hid_device*, __u8*, size_t) to int(*)(struct hid_device*, __u8*, size_t, unsigned char). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field clock_was_set has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field userspace_clients has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field alert has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_bo has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field active_bo_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field batchbuffer has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field bbaddr has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field ringbuffer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field compressed_fb has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field compressed_llb has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cur_delay has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field flip_pending_is_done has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field lvds_edid_good has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field max_delay has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field mchbar_need_disable has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field min_delay has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field no_fbc_reason has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field saveMCHBAR_RENDER_STANDBY has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_gen6 has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field uapsd_supported has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap_smps has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field req_smps has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field offchannel_ps_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field recalc_smps has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field smps_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sta_finish_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field sta_mtx has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field sta_pending_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field tmp_channel has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field tmp_channel_type has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field uapsd_max_sp_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field uapsd_queues has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field work_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field work_mtx has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field work_skb_queue has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field work_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field work_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field name has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rc_rateidx_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field min_ttl has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field data has been changed from int[24] to int[25]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field getkeycode has been changed from int(*)(struct input_dev*, int, int*) to int(*)(struct input_dev*, unsigned int, unsigned int*). | Recompilation of a client program may be broken. |
| 2 | Base type of field setkeycode has been changed from int(*)(struct input_dev*, int, int) to int(*)(struct input_dev*, unsigned int, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field filter has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field match has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cursor_height has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cursor_visble has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field cursor_width has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field cursor_x has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field cursor_y has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fib_metrics has been changed from u32[13] to u32[14]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Added const qualifier to field name. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct kset_uevent_ops::name'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sff_irq_check has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sk_dev_hash has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sk_laddr_hash has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sk_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ps_dtim_period has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field smps_mode has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field set_coverage_class has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field sta_add has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sta_remove has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Base type of field add_interface has been changed from int(*)(struct ieee80211_hw*, struct ieee80211_if_init_conf*) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Recompilation of a client program may be broken. |
| 6 | Base type of field remove_interface has been changed from void(*)(struct ieee80211_hw*, struct ieee80211_if_init_conf*) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*). | Recompilation of a client program may be broken. |
| 7 | Base type of field update_tkip_key has been changed from void(*)(struct ieee80211_hw*, struct ieee80211_key_conf*, u8 const*, u32, u16*) to void(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct ieee80211_key_conf*, struct ieee80211_sta*, u32, u16*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ap has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rate_idx_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field addr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sysfs_active has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field hugetlb_entry has been changed from int(*)(pte_t*, unsigned long, unsigned long, struct mm_walk*) to int(*)(pte_t*, unsigned long, unsigned long, unsigned long, struct mm_walk*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rss_stat has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field anon_vma_chain has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vm_prev has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field all_unreclaimable has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field pageset has been changed from struct per_cpu_pageset* to struct per_cpu_pageset. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field percpu_size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nfnl_stash has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field nfnl has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rtnl_link_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ethtool_ntuple_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ndo_get_vf_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field ndo_set_vf_mac has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field ndo_set_vf_tx_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field ndo_set_vf_vlan has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rx has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rx_np has been changed from struct netpoll* to struct list_head. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field expecting has been changed from u8[3] to u8[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field name has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field offset has been changed from u8[4] to u8[5]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field error has been changed from int(*)(struct net*, struct sk_buff*, unsigned int, enum ip_conntrack_info*, u_int8_t, unsigned int) to int(*)(struct net*, struct nf_conn*, struct sk_buff*, unsigned int, enum ip_conntrack_info*, u_int8_t, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ncommit has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cur_bus_speed has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field max_bus_speed has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field resources has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field resource has been changed from struct resource*[16] to struct resource*[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field pme_interrupt has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field run_wake has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tsleep has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field twake has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field last_tag has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attach_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field group_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mmap_user has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field mmap_locked has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flexible_groups has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field refcount has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field stop has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field start has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field async_suspend has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field completion has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mls_enabled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ignore_parity has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field quota_sync has been changed from int(*)(struct super_block*, int) to int(*)(struct super_block*, int, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field completed has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of field gpnum has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 3 | Type of field n_rcu_pending has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 4 | Type of field n_rp_cb_ready has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 5 | Type of field n_rp_cpu_needs_gp has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 6 | Type of field n_rp_gp_completed has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 7 | Type of field n_rp_gp_started has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 8 | Type of field n_rp_need_fqs has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 9 | Type of field n_rp_need_nothing has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 10 | Type of field n_rp_qs_pending has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 11 | Type of field passed_quiesc_completed has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field completed has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 2 | Type of field gpnum has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field fqs_active has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field fqs_need_gp has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field completed has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| 4 | Type of field gpnum has been changed from long to unsigned long. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field syn_ack_timeout has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_power has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field task_move_group has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field enqueue_task has been changed from void(*)(struct rq*, struct task_struct*, int) to void(*)(struct rq*, struct task_struct*, int, bool). | Recompilation of a client program may be broken. |
| 3 | Base type of field select_task_rq has been changed from int(*)(struct task_struct*, int, int) to int(*)(struct rq*, struct task_struct*, int, int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field span_weight has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rss_stat has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field epoll_watches has been changed from struct atomic_t to atomic_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field syslog has been changed from int(*)(int) to int(*)(int, bool). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field cpu_slab has been changed from struct kmem_cache_cpu* to struct kmem_cache_cpu. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[75] to unsigned long[77]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field sysctl_mem has been changed from int to long. | Recompilation of a client program may be broken. |
| 2 | Base type of field memory_allocated has been changed from struct atomic_t to struct atomic64_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field has_pfc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ops_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field present has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field suspended_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sysfs_events has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field attrs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field show has been changed from ssize_t(*)(struct sysdev_class*, char*) to ssize_t(*)(struct sysdev_class*, struct sysdev_class_attribute*, char*). | Recompilation of a client program may be broken. |
| 2 | Base type of field store has been changed from ssize_t(*)(struct sysdev_class*, char const*, size_t) to ssize_t(*)(struct sysdev_class*, struct sysdev_class_attribute*, char const*, size_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field thin_dupack has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field thin_lto has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field console has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_icount has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dcd_change has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hs_companion has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wb_start has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pci has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nmi_init has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field compat_from_user has been changed from void(*)(void*, void*) to void(*)(void*, void const*). | Recompilation of a client program may be broken. |
| 2 | Base type of field compat_to_user has been changed from int(*)(void*, void*) to int(*)(void*, void const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field priority has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field compat_from_user has been changed from void(*)(void*, void*) to void(*)(void*, void const*). | Recompilation of a client program may be broken. |
| 2 | Base type of field compat_to_user has been changed from int(*)(void*, void*) to int(*)(void*, void const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field net has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mark has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field err_handler has been changed from int(*)(struct sk_buff*, __u32) to int(*)(struct sk_buff*, u32). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 7th parameter alignf has been changed from void(*)(void*, struct resource*, resource_size_t, resource_size_t) to resource_size_t(*)(void*, struct resource const*, resource_size_t, resource_size_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter end has been changed from size_t to resource_size_t. | Recompilation of a client program may be broken. |
| 2 | Type of 2nd parameter start has been changed from size_t to resource_size_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from acpi_integer to u64. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct icmp_err[] to struct icmp_err[] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter wait has been changed from int to struct writeback_control*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter sync has been changed from int to struct writeback_control*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter scancode has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| 2 | Base type of 3rd parameter keycode has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 3rd parameter keycode has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| 2 | Type of 2nd parameter scancode has been changed from int to unsigned int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output to struct intel_encoder. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output to struct intel_encoder. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output to struct intel_encoder. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output to struct intel_encoder. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output to struct intel_encoder. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter intel_output has been changed from struct intel_output to struct intel_encoder. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 4th parameter len has been changed from u64 to loff_t. | Recompilation of a client program may be broken. |
| 2 | Type of 3rd parameter start has been changed from u64 to loff_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct sysfs_ops to struct sysfs_ops const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct mtrr_ops to struct mtrr_ops const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct mtrr_ops* to struct mtrr_ops const*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int, unsigned int*, enum sdp_header_types, enum sdp_header_types, union nf_inet_addr const*) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, enum sdp_header_types, enum sdp_header_types, union nf_inet_addr const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int*, struct nf_conntrack_expect*, struct nf_conntrack_expect*, unsigned int, unsigned int, union nf_inet_addr*) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, struct nf_conntrack_expect*, unsigned int, unsigned int, union nf_inet_addr*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int*, unsigned int, unsigned int, u_int16_t) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, unsigned int, u_int16_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int, unsigned int*, union nf_inet_addr const*) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, unsigned int, union nf_inet_addr const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int*, struct nf_conntrack_expect*, unsigned int, unsigned int) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*, struct nf_conntrack_expect*, unsigned int, unsigned int). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from unsigned int(*)(struct sk_buff*, char const**, unsigned int*) to unsigned int(*)(struct sk_buff*, unsigned int, char const**, unsigned int*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 7th parameter alignf has been changed from void(*)(void*, struct resource*, resource_size_t, resource_size_t) to resource_size_t(*)(void*, struct resource const*, resource_size_t, resource_size_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct nla_policy[21] const to struct nla_policy[23] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from unsigned char* to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct kmem_cache[14] to struct kmem_cache[28]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter arg has been changed from struct mmap_arg_struct to struct mmap_arg_struct32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int[3] to long[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct atomic_t to atomic_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int[3] to long[3]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct atomic_t to atomic_long_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from short to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_brightness became non-const. | No effect. |
| 2 | Field options became non-const. | No effect. |
| 3 | Field update_status became non-const. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cmd_type has been changed from 5 to 4. | No effect. |
| 2 | The relative position of field q has been changed from 3 to 2. | No effect. |
| 3 | The relative position of field tag has been changed from 21 to 22. | No effect. |
| 4 | The relative position of field __cmd has been changed from 25 to 24. | No effect. |
| 5 | The relative position of field atomic_flags has been changed from 6 to 5. | No effect. |
| 6 | The relative position of field ref_count has been changed from 23 to 19. | No effect. |
| 7 | The relative position of field __data_len has been changed from 8 to 7. | No effect. |
| 8 | The relative position of field cmd has been changed from 26 to 25. | No effect. |
| 9 | The relative position of field cpu has been changed from 2 to 6. | No effect. |
| 10 | The relative position of field cmd_len has been changed from 24 to 26. | No effect. |
| 11 | The relative position of field cmd_flags has been changed from 4 to 3. | No effect. |
| 12 | The relative position of field buffer has been changed from 20 to 21. | No effect. |
| 13 | The relative position of field errors has been changed from 22 to 23. | No effect. |
| 14 | The relative position of field special has been changed from 19 to 20. | No effect. |
| 15 | The relative position of field __sector has been changed from 7 to 8. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field this_arg_index has been changed from 2 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field offset has been changed from 2 to 1. | No effect. |
| 2 | The relative position of field ptr has been changed from 1 to 2. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member FIX_BTMAP_END has been changed from 2304 to 2183. | No effect. |
| 2 | Value of member FIX_BTMAP_BEGIN has been changed from 2559 to 2438. | No effect. |
| 3 | Value of member __end_of_fixed_addresses has been changed from 2560 to 2439. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field s_dirt has been changed from 4 to 2. | No effect. |
| 2 | The relative position of field s_time_gran has been changed from 37 to 36. | No effect. |
| 3 | The relative position of field s_blocksize has been changed from 2 to 4. | No effect. |
| 4 | The relative position of field s_vfs_rename_mutex has been changed from 36 to 37. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field ht_smps has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field inet_id has been changed from 11 to 10. | No effect. |
| 2 | The relative position of field inet_sport has been changed from 10 to 9. | No effect. |
| 3 | The relative position of field opt has been changed from 9 to 11. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field busy has been changed from 9 to 7. | No effect. |
| 2 | The relative position of field cursor_addr has been changed from 4 to 13. | No effect. |
| 3 | The relative position of field cursor_bo has been changed from 3 to 12. | No effect. |
| 4 | The relative position of field dpms_mode has been changed from 8 to 6. | No effect. |
| 5 | The relative position of field idle_timer has been changed from 10 to 8. | No effect. |
| 6 | The relative position of field lowfreq_avail has been changed from 11 to 9. | No effect. |
| 7 | The relative position of field lut_b has been changed from 7 to 5. | No effect. |
| 8 | The relative position of field lut_g has been changed from 6 to 4. | No effect. |
| 9 | The relative position of field lut_r has been changed from 5 to 3. | No effect. |
| 10 | The relative position of field overlay has been changed from 12 to 10. | No effect. |
| 11 | The relative position of field unpin_work has been changed from 13 to 11. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field last_waited has been changed from 5 to 6. | No effect. |
| 2 | The relative position of field nr_batch_requests has been changed from 6 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member NF_CT_EXT_ZONE with value 4 has been added. | No effect. |
| 2 | Value of member NF_CT_EXT_NUM has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member SIP_HDR_VIA_TCP with value 5 has been added. | No effect. |
| 2 | Value of member SIP_HDR_CONTENT_LENGTH has been changed from 6 to 7. | No effect. |
| 3 | Value of member SIP_HDR_EXPIRES has been changed from 5 to 6. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field info has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member POWER_SUPPLY_PROP_CYCLE_COUNT with value 6 has been added. | No effect. |
| 2 | Value of member POWER_SUPPLY_PROP_CHARGE_COUNTER has been changed from 22 to 23. | No effect. |
| 3 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MAX has been changed from 6 to 7. | No effect. |
| 4 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MAX_DESIGN has been changed from 8 to 9. | No effect. |
| 5 | Value of member POWER_SUPPLY_PROP_CAPACITY has been changed from 29 to 30. | No effect. |
| 6 | Value of member POWER_SUPPLY_PROP_CAPACITY_LEVEL has been changed from 30 to 31. | No effect. |
| 7 | Value of member POWER_SUPPLY_PROP_CHARGE_AVG has been changed from 21 to 22. | No effect. |
| 8 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY has been changed from 19 to 20. | No effect. |
| 9 | Value of member POWER_SUPPLY_PROP_CHARGE_EMPTY_DESIGN has been changed from 17 to 18. | No effect. |
| 10 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL has been changed from 18 to 19. | No effect. |
| 11 | Value of member POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN has been changed from 16 to 17. | No effect. |
| 12 | Value of member POWER_SUPPLY_PROP_CHARGE_NOW has been changed from 20 to 21. | No effect. |
| 13 | Value of member POWER_SUPPLY_PROP_CURRENT_AVG has been changed from 13 to 14. | No effect. |
| 14 | Value of member POWER_SUPPLY_PROP_CURRENT_NOW has been changed from 12 to 13. | No effect. |
| 15 | Value of member POWER_SUPPLY_PROP_ENERGY_AVG has been changed from 28 to 29. | No effect. |
| 16 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY has been changed from 26 to 27. | No effect. |
| 17 | Value of member POWER_SUPPLY_PROP_ENERGY_EMPTY_DESIGN has been changed from 24 to 25. | No effect. |
| 18 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL has been changed from 25 to 26. | No effect. |
| 19 | Value of member POWER_SUPPLY_PROP_ENERGY_FULL_DESIGN has been changed from 23 to 24. | No effect. |
| 20 | Value of member POWER_SUPPLY_PROP_ENERGY_NOW has been changed from 27 to 28. | No effect. |
| 21 | Value of member POWER_SUPPLY_PROP_MANUFACTURER has been changed from 38 to 39. | No effect. |
| 22 | Value of member POWER_SUPPLY_PROP_MODEL_NAME has been changed from 37 to 38. | No effect. |
| 23 | Value of member POWER_SUPPLY_PROP_POWER_AVG has been changed from 15 to 16. | No effect. |
| 24 | Value of member POWER_SUPPLY_PROP_POWER_NOW has been changed from 14 to 15. | No effect. |
| 25 | Value of member POWER_SUPPLY_PROP_SERIAL_NUMBER has been changed from 39 to 40. | No effect. |
| 26 | Value of member POWER_SUPPLY_PROP_TEMP has been changed from 31 to 32. | No effect. |
| 27 | Value of member POWER_SUPPLY_PROP_TEMP_AMBIENT has been changed from 32 to 33. | No effect. |
| 28 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_AVG has been changed from 34 to 35. | No effect. |
| 29 | Value of member POWER_SUPPLY_PROP_TIME_TO_EMPTY_NOW has been changed from 33 to 34. | No effect. |
| 30 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_AVG has been changed from 36 to 37. | No effect. |
| 31 | Value of member POWER_SUPPLY_PROP_TIME_TO_FULL_NOW has been changed from 35 to 36. | No effect. |
| 32 | Value of member POWER_SUPPLY_PROP_VOLTAGE_AVG has been changed from 11 to 12. | No effect. |
| 33 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MIN has been changed from 7 to 8. | No effect. |
| 34 | Value of member POWER_SUPPLY_PROP_VOLTAGE_MIN_DESIGN has been changed from 9 to 10. | No effect. |
| 35 | Value of member POWER_SUPPLY_PROP_VOLTAGE_NOW has been changed from 10 to 11. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field tk_callback has been changed from 9 to 10. | No effect. |
| 2 | The relative position of field tk_waitqueue has been changed from 17 to 18. | No effect. |
| 3 | The relative position of field tk_rtt has been changed from 22 to 23. | No effect. |
| 4 | The relative position of field tk_start has been changed from 21 to 22. | No effect. |
| 5 | The relative position of field tk_workqueue has been changed from 16 to 17. | No effect. |
| 6 | The relative position of field tk_action has been changed from 10 to 11. | No effect. |
| 7 | The relative position of field tk_timeouts has been changed from 19 to 20. | No effect. |
| 8 | The relative position of field tk_runstate has been changed from 15 to 16. | No effect. |
| 9 | The relative position of field tk_flags has been changed from 14 to 15. | No effect. |
| 10 | The relative position of field tk_ops has been changed from 11 to 12. | No effect. |
| 11 | The relative position of field tk_owner has been changed from 23 to 24. | No effect. |
| 12 | The relative position of field tk_priority has been changed from 24 to 25. | No effect. |
| 13 | The relative position of field u has been changed from 18 to 19. | No effect. |
| 14 | The relative position of field tk_bytes_sent has been changed from 20 to 21. | No effect. |
| 15 | The relative position of field tk_calldata has been changed from 12 to 13. | No effect. |
| 16 | The relative position of field tk_rebind_retry has been changed from 25 to 9. | No effect. |
| 17 | The relative position of field tk_timeout has been changed from 13 to 14. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cpu_slab has been changed from 18 to 0. | No effect. |
| 2 | The relative position of field objsize has been changed from 2 to 3. | No effect. |
| 3 | The relative position of field offset has been changed from 3 to 4. | No effect. |
| 4 | The relative position of field size has been changed from 1 to 2. | No effect. |
| 5 | The relative position of field flags has been changed from 0 to 1. | No effect. |
| 6 | The relative position of field oo has been changed from 4 to 5. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field s_ino has been changed from 7 to 8. | No effect. |
| 2 | The relative position of field s_mode has been changed from 8 to 7. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter max_sectors has been renamed to max_hw_sectors. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter offset has been renamed to start. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to resource_size_t. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter wait has been renamed to wbc. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter sync has been renamed to wbc. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter intel_output has been renamed to intel_encoder. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter output_device has been renamed to sdvo_reg. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter pagenr has been renamed to pfn. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter group_leader has been renamed to leader. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to sdata. | No effect. |