| Module Name | vmlinux |
|---|---|
| Version #1 | 3.9.11 |
| Version #2 | 3.10.19 |
| CPU Type | x86 |
| Subject | Binary Compatibility |
| Total Header Files | 790 |
|---|---|
| Total Source Files | 1453 |
| Total Objects | 1 |
| Total Symbols / Types | 16369 / 9220 |
| Verdict | Incompatible (51.7%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 686 |
| Removed Symbols | High | 191 |
| Problems with Data Types | High | 69 |
| Medium | 651 | |
| Low | 409 | |
| Problems with Symbols | High | 27 |
| Medium | 3035 | |
| Low | 45 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 4 |
| Change | Effect | |
|---|---|---|
| 1 | Field param_count 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 ki_batch 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 ki_flags 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 ki_key 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 ki_retry 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 ki_run_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 active_reqs 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 ctx_lock 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 mm 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 ring_info 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 run_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. |
| 6 | Field wait 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 wq 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 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 wakeup_timer 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 last_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. |
| 3 | Field 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 user_modes 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 io_page 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 add_in_jack_modes 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 add_out_jack_modes 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 shared_mic_hp 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 detach_adapter 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 backlight_enabled 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 backlight_level 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 hotplug_supported_mask 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 num_pipe 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 pipestat 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 skb 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 timers_running 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 _oper_channel 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 _oper_channel_type 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 csa_channel 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 napi 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 napi_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 cf_params 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 cf_params_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. |
| 3 | Field ds_params_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. |
| 4 | Field erp_info_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. |
| 5 | Field fh_params 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 fh_params_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. |
| 7 | Field ibss_params 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. |
| 8 | Field ibss_params_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. |
| 9 | Field num_of_quiet_elem 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. |
| 10 | Field quiet_elem 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. |
| 11 | Field quiet_elem_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. |
| 12 | Field timeout_int_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 bpp 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 rs_lock 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 b_cow_tid 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 channel 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 channel_type 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 free_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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field read_proc 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 pde_users 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 wakemask 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 page 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 cred 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 entry 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 nr_events 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 buffer 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 time_start 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 worker_ida 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 assoc_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field pool_wq 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 mayday_mask 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 flush_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field rebind_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 | Parameter uid of type kuid_t* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter policy of type struct cpufreq_policy* 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 | The parameter msg became passed at the different offset on the stack (-24 instead of -20). | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter minor_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 phys_addr of type u64 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 handle of type handle_t* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter endtime of type time_t* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qop 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 handle of type handle_t* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter key has been changed from struct ieee80211_key* (4 bytes) to bool (1 byte). | 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 start of type unsigned long 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 req of type struct cfg80211_assoc_request* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 5th middle parameter prev_bssid 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 req of type struct cfg80211_assoc_request* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| 2 | 5th middle parameter prev_bssid 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 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 local of type struct ieee80211_local* 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 opos of type loff_t* has been added to the calling stack at the middle position. | Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd middle parameter hvpp 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 rvp 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 tr of type struct trace_array* 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 queues of type unsigned long 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 queues of type unsigned long 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 action of type bool 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 argument_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field return_btype 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 info has been changed from 6 bytes to 7 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field ret_info has been changed from 6 bytes to 7 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field ret_info2 has been changed from 6 bytes to 7 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 4 | Size of field ret_info3 has been changed from 6 bytes to 7 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 dev has been changed from 224 bytes to 228 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 physical_node_lock has been changed from 20 bytes to 24 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 | Size of field pnp has been changed from 92 bytes to 96 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 bus_address 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 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 agp_mutex has been changed from 20 bytes to 24 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 ki_users has been changed from int to struct atomic_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_base 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 nr_events 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 nr_pages 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 ring_pages 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 | Type of field dead has been changed from int to struct atomic_t of different format. | This field may be incorrectly initialized or accessed by applications. |
| 6 | The relative position of field max_reqs has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field preallocated_names has been changed from 380 bytes to 400 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 name_put has been changed from 13 to 3. | 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 rdev has been changed from 7 to 9. | 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 fcap_ver has been changed from 10 to 12. | 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 fcap has been changed from 9 to 11. | 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 ino 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. |
| 6 | The relative position of field mode has been changed from 4 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 uid has been changed from 5 to 7. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field gid has been changed from 6 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field dev has been changed from 3 to 5. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field osid has been changed from 8 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field type has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field name_len has been changed from 11 to 2. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field pipe_mutex has been changed from 20 bytes to 24 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 wq_mutex has been changed from 20 bytes to 24 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 wb has been changed from 100 bytes to 116 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 dwork 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 ops_lock has been changed from 20 bytes to 24 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 update_lock has been changed from 20 bytes to 24 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 | Size of field dev has been changed from 224 bytes to 228 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 mutex has been changed from 20 bytes to 24 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 sysfs_lock has been changed from 20 bytes to 24 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 backing_dev_info has been changed from 380 bytes to 396 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 user_mpm 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 224 bytes to 228 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field vht_capa_mod_mask 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 mtx has been changed from 20 bytes to 24 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 cgroup_ida has been changed from 28 bytes to 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. |
| 2 | Size of field top_cgroup has been changed from 176 bytes to 180 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 pidlist_mutex has been changed from 20 bytes to 24 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 top_cgroup 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 active has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field port has been changed from 168 bytes to 176 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 224 bytes to 228 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 crit_proto_nlportid 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 devlist_mtx has been changed from 20 bytes to 24 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 | Size of field mtx has been changed from 20 bytes to 24 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 sched_scan_mtx has been changed from 20 bytes to 24 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 power_lock has been changed from 20 bytes to 24 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 224 bytes to 228 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 governor_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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field timer_mutex has been changed from 20 bytes to 24 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 mutex has been changed from 20 bytes to 24 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 get_cpu_cdbs 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 get_cpu_dbs_info_s 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. |
| 4 | Field gov_check_cpu 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. |
| 5 | Field gov_dbs_timer 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. |
| 6 | Field gov_ops 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 kobjs has been changed from struct cpuidle_state_kobj*[8] (32 bytes) to struct cpuidle_state_kobj*[10] (40 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 | Type of field states_usage has been changed from struct cpuidle_state_usage[8] (192 bytes) to struct cpuidle_state_usage[10] (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 | Type of field states has been changed from struct cpuidle_state[8] (608 bytes) to struct cpuidle_state[10] (760 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 mutex has been changed from 20 bytes to 24 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 suspend_lock has been changed from 20 bytes to 24 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 type_lock has been changed from 20 bytes to 24 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 lock has been changed from 20 bytes to 24 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 kdev has been changed from 224 bytes to 228 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 mutex has been changed from 20 bytes to 24 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 crtc_idr has been changed from 24 bytes to 28 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 fb_lock has been changed from 20 bytes to 24 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 | Size of field idr_mutex has been changed from 20 bytes to 24 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 mutex has been changed from 20 bytes to 24 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 mode_config has been changed from 352 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 struct_mutex has been changed from 20 bytes to 24 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 | Size of field ctxlist_mutex has been changed from 20 bytes to 24 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 ctx_idr has been changed from 24 bytes to 28 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 object_name_idr has been changed from 24 bytes to 28 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 fbs_lock has been changed from 20 bytes to 24 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 object_idr has been changed from 24 bytes to 28 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 | Size of field prime has been changed from 28 bytes to 32 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 debugfs_lock has been changed from 20 bytes to 24 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 kdev has been changed from 224 bytes to 228 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 lock has been changed from 20 bytes to 24 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 dev has been changed from 224 bytes to 228 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 dynids has been changed from 28 bytes to 32 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 lock has been changed from 20 bytes to 24 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 mutex has been changed from 20 bytes to 24 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 sysfs_lock has been changed from 20 bytes to 24 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 224 bytes to 228 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 vfs_inode has been changed from 328 bytes to 336 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 num_io_pages 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 pages 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 s_orphan_lock has been changed from 20 bytes to 24 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Field s_resv_clusters 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 | The relative position of field allow_utime has been changed from 10 to 11. | 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 nfs has been changed from 25 to 10. | 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 discard has been changed from 24 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field dotsOK has been changed from 14 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field flush has been changed from 19 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field isvfat has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field nocase has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field numtail has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field quiet has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field rodir has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field showexec has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field sys_immutable has been changed from 13 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field tz_set has been changed from 22 to 23. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field unicode_xlate has been changed from 17 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field usefree has been changed from 21 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field utf8 has been changed from 16 to 17. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field nfs_build_inode_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. |
| 2 | Size of field fat_lock has been changed from 20 bytes to 24 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 | Size of field options has been changed from 32 bytes to 36 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 s_lock has been changed from 20 bytes to 24 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 lock has been changed from 20 bytes to 24 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 mm_lock has been changed from 20 bytes to 24 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 next 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 fdtab has been changed from 28 bytes to 24 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 FIX_BTMAP_BEGIN has been changed from 488 to 489. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member FIX_KMAP_BEGIN has been changed from 70 to 71. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 3 | Value of member FIX_PCIE_MCFG has been changed from 230 to 231. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 4 | Value of member FIX_TEXT_POKE0 has been changed from 232 to 233. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 5 | Value of member FIX_TEXT_POKE1 has been changed from 231 to 232. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 6 | Value of member FIX_WP_TEST has been changed from 489 to 490. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 7 | Value of member __end_of_fixed_addresses has been changed from 490 to 491. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 8 | Value of member __end_of_permanent_fixed_addresses has been changed from 233 to 234. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field i_mmap_mutex has been changed from 20 bytes to 24 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 bd_mutex has been changed from 20 bytes to 24 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 bd_fsfreeze_mutex has been changed from 20 bytes to 24 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 i_mutex has been changed from 20 bytes to 24 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | Size of field i_data has been changed from 92 bytes to 96 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 s_vfs_rename_mutex has been changed from 20 bytes to 24 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 s_dquot has been changed from 172 bytes to 180 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 mark_mutex has been changed from 20 bytes to 24 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 notification_mutex has been changed from 20 bytes to 24 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 last_wd has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir 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 trace_buffer 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 mutex has been changed from 20 bytes to 24 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 | The relative position of field cpu has been changed from 13 to 15. | 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 ent_size has been changed from 12 to 14. | 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 idx has been changed from 16 to 18. | 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 pos has been changed from 15 to 17. | 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 seq has been changed from 8 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 snapshot has been changed from 18 to 9. | 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 started has been changed from 17 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 ts has been changed from 14 to 16. | 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 ent has been changed from 9 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field leftover has been changed from 11 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field lost_events has been changed from 10 to 12. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field block_mutex has been changed from 20 bytes to 24 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 part0 has been changed from 300 bytes to 304 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 224 bytes to 228 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 gm_oid has been changed from struct xdr_netobj (8 bytes) to struct rpcsec_gss_oid (36 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 qop 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 kvm_posted_intr_ipis 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 inputs 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 and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mutex has been changed from 20 bytes to 24 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 cmd_mutex has been changed from 20 bytes to 24 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 prepare_mutex has been changed from 20 bytes to 24 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 control_mutex has been changed from 20 bytes to 24 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 hash_mutex has been changed from 20 bytes to 24 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 | Size of field spdif_mutex has been changed from 20 bytes to 24 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 user_mutex has been changed from 20 bytes to 24 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 stream has been changed from 104 bytes to 112 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 ops has been changed from 16 bytes to 20 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 add_jack_modes 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 beep_nid 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 extra_out_badness 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 hp_mic 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 hp_mic_mux_idx 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 main_out_badness 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 suppress_hp_mic_detect 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 | Size of field autocfg has been changed from 144 bytes to 176 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 9 | Size of field pcm_mutex has been changed from 20 bytes to 24 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. |
| 10 | Size of field pcm_rec has been changed from 372 bytes to 396 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 channels has been changed from int (4 bytes) to u8 (1 byte). | 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 | Type of field format has been changed from int (4 bytes) to u8 (1 byte). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 3 | Field max_bitrate 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. |
| 4 | Field profile 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. |
| 5 | Field rates 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. |
| 6 | Field sample_bits 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. |
| 7 | The relative position of field channels has been changed from 0 to 1. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field format has been changed from 1 to 0. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field lock has been changed from 20 bytes to 24 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 debug_list_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. |
| 2 | Field driver_input_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 io_started 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 224 bytes to 228 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 clock_base has been changed from struct hrtimer_clock_base[3] (144 bytes) to struct hrtimer_clock_base[4] (192 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 wakeup_enabled_descendants 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 status_mutex has been changed from 20 bytes to 24 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 224 bytes to 228 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 open_mutex has been changed from 20 bytes to 24 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 224 bytes to 228 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 userspace_clients_lock has been changed from 20 bytes to 24 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 224 bytes to 228 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 get_pipe_config 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 fence_reg has been changed from 5 bits to 6 bits. | 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 ctx 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 ring has been changed from 48 bytes to 60 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 | Type of field fence has been changed from u64[16] (128 bytes) to u64[32] (256 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 hotplug_reenable_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. |
| 2 | Field hpd_stats 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 num_plane 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 display has been changed from 76 bytes to 80 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 dpio_lock has been changed from 20 bytes to 24 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. |
| 6 | Size of field gmbus has been changed from 2472 bytes to 2544 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. |
| 7 | Size of field gmbus_mutex has been changed from 20 bytes to 24 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. |
| 8 | Size of field modeset_restore_lock has been changed from 20 bytes to 24 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. |
| 9 | Size of field regfile has been changed from 2956 bytes to 3084 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. |
| 10 | Size of field rps has been changed from 124 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. |
| 11 | Type of field fence_regs has been changed from struct drm_i915_fence_reg[16] (256 bytes) to struct drm_i915_fence_reg[32] (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. |
| 12 | The relative position of field bios_lvds_val has been changed from 46 to 47. | 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 child_dev has been changed from 79 to 80. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 14 | The relative position of field compressed_llb has been changed from 86 to 87. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 15 | The relative position of field console_resume_work has been changed from 89 to 90. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 16 | The relative position of field crt_ddc_pin has been changed from 49 to 50. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 17 | The relative position of field ddi_plls has been changed from 73 to 74. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 18 | The relative position of field display has been changed from 57 to 58. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 19 | The relative position of field edp has been changed from 47 to 48. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 20 | The relative position of field fbdev has been changed from 88 to 89. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 21 | The relative position of field fence_regs has been changed from 50 to 51. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 22 | The relative position of field gpu_error has been changed from 87 to 88. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 23 | The relative position of field gtt has been changed from 63 to 64. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 24 | The relative position of field ips has been changed from 83 to 84. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 25 | The relative position of field l3_parity has been changed from 81 to 82. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 26 | The relative position of field lvds_downclock has been changed from 76 to 77. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 27 | The relative position of field lvds_downclock_avail has been changed from 75 to 76. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 28 | The relative position of field mchbar_need_disable has been changed from 80 to 81. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 29 | The relative position of field mm has been changed from 64 to 65. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 30 | The relative position of field modeset_restore has been changed from 61 to 62. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 31 | The relative position of field modeset_restore_lock has been changed from 62 to 63. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 32 | The relative position of field no_aux_handshake has been changed from 48 to 49. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 33 | The relative position of field orig_clock has been changed from 77 to 78. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 34 | The relative position of field pch_id has been changed from 59 to 60. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 35 | The relative position of field pch_pf_size has been changed from 68 to 69. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 36 | The relative position of field pch_plls has been changed from 72 to 73. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 37 | The relative position of field pch_type has been changed from 58 to 59. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 38 | The relative position of field pending_flip_queue has been changed from 71 to 72. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 39 | The relative position of field rps has been changed from 82 to 83. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 40 | The relative position of field sdvo_mappings has been changed from 65 to 66. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 41 | The relative position of field wq has been changed from 56 to 57. | 1) Applications will access incorrect memory when attempting to access this field. 2) Size of the inclusive type has been changed. |
| 42 | The relative position of field backlight has been changed from 90 to 36. | Applications will access incorrect memory when attempting to access this field. |
| 43 | The relative position of field child_dev_num has been changed from 78 to 79. | Applications will access incorrect memory when attempting to access this field. |
| 44 | The relative position of field compressed_fb has been changed from 85 to 86. | Applications will access incorrect memory when attempting to access this field. |
| 45 | The relative position of field display_clock_mode has been changed from 43 to 44. | Applications will access incorrect memory when attempting to access this field. |
| 46 | The relative position of field fdi_rx_polarity_inverted has been changed from 44 to 45. | Applications will access incorrect memory when attempting to access this field. |
| 47 | The relative position of field fence_reg_start has been changed from 51 to 52. | Applications will access incorrect memory when attempting to access this field. |
| 48 | The relative position of field fsb_freq has been changed from 53 to 54. | Applications will access incorrect memory when attempting to access this field. |
| 49 | The relative position of field int_crt_support has been changed from 41 to 42. | Applications will access incorrect memory when attempting to access this field. |
| 50 | The relative position of field int_tv_support has been changed from 38 to 39. | Applications will access incorrect memory when attempting to access this field. |
| 51 | The relative position of field is_ddr3 has been changed from 55 to 56. | Applications will access incorrect memory when attempting to access this field. |
| 52 | The relative position of field lfp_lvds_vbt_mode has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 53 | The relative position of field lvds_border_bits has been changed from 66 to 67. | Applications will access incorrect memory when attempting to access this field. |
| 54 | The relative position of field lvds_dither has been changed from 39 to 40. | Applications will access incorrect memory when attempting to access this field. |
| 55 | The relative position of field lvds_ssc_freq has been changed from 45 to 46. | Applications will access incorrect memory when attempting to access this field. |
| 56 | The relative position of field lvds_use_ssc has been changed from 42 to 43. | Applications will access incorrect memory when attempting to access this field. |
| 57 | The relative position of field lvds_vbt has been changed from 40 to 41. | Applications will access incorrect memory when attempting to access this field. |
| 58 | The relative position of field mem_freq has been changed from 54 to 55. | Applications will access incorrect memory when attempting to access this field. |
| 59 | The relative position of field no_fbc_reason has been changed from 84 to 85. | Applications will access incorrect memory when attempting to access this field. |
| 60 | The relative position of field num_fence_regs has been changed from 52 to 53. | Applications will access incorrect memory when attempting to access this field. |
| 61 | The relative position of field pch_pf_pos has been changed from 67 to 68. | Applications will access incorrect memory when attempting to access this field. |
| 62 | The relative position of field pipe_to_crtc_mapping has been changed from 70 to 71. | Applications will access incorrect memory when attempting to access this field. |
| 63 | The relative position of field plane_to_crtc_mapping has been changed from 69 to 70. | Applications will access incorrect memory when attempting to access this field. |
| 64 | The relative position of field quirks has been changed from 60 to 61. | Applications will access incorrect memory when attempting to access this field. |
| 65 | The relative position of field render_reclock_avail has been changed from 74 to 75. | Applications will access incorrect memory when attempting to access this field. |
| 66 | The relative position of field sdvo_lvds_vbt_mode has been changed from 37 to 38. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field enable 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 saveFENCE has been changed from uint64_t[16] (128 bytes) to uint64_t[32] (256 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 num_pipes 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 hw_lock has been changed from 20 bytes to 24 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 adapter has been changed from 360 bytes to 372 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 idmap_mutex has been changed from 20 bytes to 24 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 idr has been changed from 24 bytes to 28 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 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 element_id 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 length 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 sw_elem 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 chan_switch has been changed from 6 bytes to 1 byte. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mtx has been changed from 20 bytes to 24 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 timer_running 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 mtx has been changed from 20 bytes to 24 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 | Type of field p2p_noa_index has been changed from u8 (1 byte) to s16 (2 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 3 | Field timers_running 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 user_mpm 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 mtx has been changed from 20 bytes to 24 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 _oper_chandef 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 csa_chandef 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 ack_status_frames has been changed from 24 bytes to 28 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 chanctx_mtx has been changed from 20 bytes to 24 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 hw has been changed from 104 bytes to 116 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. |
| 6 | Size of field iflist_mtx has been changed from 20 bytes to 24 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. |
| 7 | Size of field key_mtx has been changed from 20 bytes to 24 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. |
| 8 | Size of field mtx has been changed from 20 bytes to 24 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. |
| 9 | Size of field sta_mtx has been changed from 20 bytes to 24 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 tx_conf has been changed from 32 bytes to 40 bytes. | 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 u has been changed from 712 bytes to 716 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 3 | Size of field wdev has been changed from 188 bytes to 192 bytes. | Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 4 | Field crypto_tx_tailroom_pending_dec 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. |
| 5 | Field dec_tailroom_needed_wk 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. |
| 6 | Field rc_has_mcs_mask 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. |
| 7 | Field suspend_bss_conf 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 rate 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 ext_chansw_ie 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 sec_chan_offs 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 wide_bw_chansw_ie 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 ibss has been changed from 172 bytes to 168 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| 2 | Size of field mesh has been changed from 712 bytes to 716 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 3 | Size of field mgd has been changed from 476 bytes to 500 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 token 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 tokenized 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 icsk_inet has been changed from 556 bytes to 560 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 hash has been changed from struct hlist_head[64] (256 bytes) to struct inet_frag_bucket[1024] (8192 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 sk has been changed from 420 bytes to 424 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 access has been changed from 20 bytes to 24 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 mutex has been changed from 20 bytes to 24 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 224 bytes to 228 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 mutex has been changed from 20 bytes to 24 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 base has been changed from 864 bytes to 860 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 | Field config 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 base has been changed from 788 bytes to 792 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 3 | Field cpu_transcoder 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 base has been changed from 92 bytes to 104 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 dp has been changed from 544 bytes to 560 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 aux_ch_ctl_reg 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 adapter has been changed from 360 bytes to 372 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 compute_config 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 mode_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 mutex has been changed from 20 bytes to 24 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 cons_lock has been changed from 20 bytes to 24 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 dest_trash_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. |
| 2 | Field dest_trash_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. |
| 3 | Size of field sync_mutex has been changed from 20 bytes to 24 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 | Type of field rs_table has been changed from struct list_head[16] (128 bytes) to struct hlist_head[16] (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 | Size of field ipcs_idr has been changed from 24 bytes to 28 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 ids has been changed from 156 bytes to 168 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 j_checkpoint_mutex has been changed from 20 bytes to 24 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 j_barrier has been changed from 20 bytes to 24 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 tdev has been changed from 224 bytes to 228 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 eh_mutex has been changed from 20 bytes to 24 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 tdev has been changed from 224 bytes to 228 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 device has been changed from 2720 bytes to 2728 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 link has been changed from 3300 bytes to 3312 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 scsi_scan_mutex has been changed from 20 bytes to 24 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 | Size of field tdev has been changed from 224 bytes to 228 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 cmd_mutex has been changed from 20 bytes to 24 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 f_mutex has been changed from 20 bytes to 24 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 h_mutex has been changed from 20 bytes to 24 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 pad 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 p2p_ctwindow 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 p2p_oppps has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field chandef 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 conf has been changed from 40 bytes to 48 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 set_multicast_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. |
| Change | Effect | |
|---|---|---|
| 1 | Field acm 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 rate_idx_mcs_mask has been changed from u8[10] (10 bytes) to u8* (4 bytes). | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| 2 | The pointer level of field rate_idx_mcs_mask has been increased from 0 to 1. | The library functions may try to access unallocated memory by the dereferencing of old field value and therefore cause a crash of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field bss_conf has been changed from 152 bytes to 204 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 lg_mutex has been changed from 20 bytes to 24 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 mutex has been changed from 20 bytes to 24 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 bitmap_info has been changed from 64 bytes to 68 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 open_mutex has been changed from 20 bytes to 24 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 | Size of field reconfig_mutex has been changed from 20 bytes to 24 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 reg_mutex has been changed from 20 bytes to 24 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 mmap_legacy_base 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 context has been changed from 32 bytes to 36 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 lock has been changed from 20 bytes to 24 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 mnt_mp 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 nf 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 packet has been changed from 24 bytes to 28 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 224 bytes to 228 bytes. | 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 _rx has been changed from 59 to 58. | Applications will access incorrect memory when attempting to access this field. |
| 3 | The relative position of field _tx has been changed from 66 to 65. | Applications will access incorrect memory when attempting to access this field. |
| 4 | The relative position of field addr_assign_type has been changed from 37 to 38. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field addr_len has been changed from 38 to 39. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field addr_list_lock has been changed from 41 to 42. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field allmulti has been changed from 46 to 49. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field atalk_ptr has been changed from 47 to 50. | Applications will access incorrect memory when attempting to access this field. |
| 9 | The relative position of field ax25_ptr has been changed from 51 to 54. | Applications will access incorrect memory when attempting to access this field. |
| 10 | The relative position of field broadcast has been changed from 57 to 64. | Applications will access incorrect memory when attempting to access this field. |
| 11 | The relative position of field dev_addr has been changed from 55 to 57. | Applications will access incorrect memory when attempting to access this field. |
| 12 | The relative position of field dev_addrs has been changed from 56 to 45. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field dev_id has been changed from 40 to 41. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field dma has been changed from 30 to 31. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field dn_ptr has been changed from 49 to 52. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field ethtool_ops has been changed from 21 to 22. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field features has been changed from 11 to 12. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field flags has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field gflags has been changed from 25 to 26. | Applications will access incorrect memory when attempting to access this field. |
| 20 | The relative position of field hard_header_len has been changed from 33 to 34. | Applications will access incorrect memory when attempting to access this field. |
| 21 | The relative position of field header_ops has been changed from 22 to 23. | Applications will access incorrect memory when attempting to access this field. |
| 22 | The relative position of field hw_enc_features has been changed from 15 to 16. | Applications will access incorrect memory when attempting to access this field. |
| 23 | The relative position of field hw_features has been changed from 12 to 13. | Applications will access incorrect memory when attempting to access this field. |
| 24 | The relative position of field ieee80211_ptr has been changed from 52 to 55. | Applications will access incorrect memory when attempting to access this field. |
| 25 | The relative position of field if_port has been changed from 29 to 30. | Applications will access incorrect memory when attempting to access this field. |
| 26 | The relative position of field ifindex has been changed from 16 to 17. | Applications will access incorrect memory when attempting to access this field. |
| 27 | The relative position of field iflink has been changed from 17 to 18. | Applications will access incorrect memory when attempting to access this field. |
| 28 | The relative position of field ingress_queue has been changed from 65 to 63. | Applications will access incorrect memory when attempting to access this field. |
| 29 | The relative position of field ip6_ptr has been changed from 50 to 53. | Applications will access incorrect memory when attempting to access this field. |
| 30 | The relative position of field ip_ptr has been changed from 48 to 51. | Applications will access incorrect memory when attempting to access this field. |
| 31 | The relative position of field last_rx has been changed from 53 to 56. | Applications will access incorrect memory when attempting to access this field. |
| 32 | The relative position of field link_mode has been changed from 28 to 29. | Applications will access incorrect memory when attempting to access this field. |
| 33 | The relative position of field mc has been changed from 43 to 44. | Applications will access incorrect memory when attempting to access this field. |
| 34 | The relative position of field mtu has been changed from 31 to 32. | Applications will access incorrect memory when attempting to access this field. |
| 35 | The relative position of field needed_headroom has been changed from 34 to 35. | Applications will access incorrect memory when attempting to access this field. |
| 36 | The relative position of field needed_tailroom has been changed from 35 to 36. | Applications will access incorrect memory when attempting to access this field. |
| 37 | The relative position of field netdev_ops has been changed from 20 to 21. | Applications will access incorrect memory when attempting to access this field. |
| 38 | The relative position of field num_rx_queues has been changed from 60 to 59. | Applications will access incorrect memory when attempting to access this field. |
| 39 | The relative position of field num_tx_queues has been changed from 67 to 66. | Applications will access incorrect memory when attempting to access this field. |
| 40 | The relative position of field operstate has been changed from 27 to 28. | Applications will access incorrect memory when attempting to access this field. |
| 41 | The relative position of field padded has been changed from 26 to 27. | Applications will access incorrect memory when attempting to access this field. |
| 42 | The relative position of field perm_addr has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 43 | The relative position of field promiscuity has been changed from 45 to 48. | Applications will access incorrect memory when attempting to access this field. |
| 44 | The relative position of field qdisc has been changed from 69 to 68. | Applications will access incorrect memory when attempting to access this field. |
| 45 | The relative position of field queues_kset has been changed from 58 to 46. | Applications will access incorrect memory when attempting to access this field. |
| 46 | The relative position of field real_num_rx_queues has been changed from 61 to 60. | Applications will access incorrect memory when attempting to access this field. |
| 47 | The relative position of field real_num_tx_queues has been changed from 68 to 67. | Applications will access incorrect memory when attempting to access this field. |
| 48 | The relative position of field rx_cpu_rmap has been changed from 62 to 72. | Applications will access incorrect memory when attempting to access this field. |
| 49 | The relative position of field rx_dropped has been changed from 19 to 20. | Applications will access incorrect memory when attempting to access this field. |
| 50 | The relative position of field rx_handler has been changed from 63 to 61. | Applications will access incorrect memory when attempting to access this field. |
| 51 | The relative position of field rx_handler_data has been changed from 64 to 62. | Applications will access incorrect memory when attempting to access this field. |
| 52 | The relative position of field stats has been changed from 18 to 19. | Applications will access incorrect memory when attempting to access this field. |
| 53 | The relative position of field tx_global_lock has been changed from 71 to 70. | Applications will access incorrect memory when attempting to access this field. |
| 54 | The relative position of field tx_queue_len has been changed from 70 to 69. | Applications will access incorrect memory when attempting to access this field. |
| 55 | The relative position of field type has been changed from 32 to 33. | Applications will access incorrect memory when attempting to access this field. |
| 56 | The relative position of field uc has been changed from 42 to 43. | Applications will access incorrect memory when attempting to access this field. |
| 57 | The relative position of field uc_promisc has been changed from 44 to 47. | Applications will access incorrect memory when attempting to access this field. |
| 58 | The relative position of field upper_dev_list has been changed from 54 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 59 | The relative position of field vlan_features has been changed from 14 to 15. | Applications will access incorrect memory when attempting to access this field. |
| 60 | The relative position of field wanted_features has been changed from 13 to 14. | Applications will access incorrect memory when attempting to access this field. |
| 61 | The relative position of field xps_maps has been changed from 72 to 71. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field dev_lock has been changed from struct mutex (20 bytes) to struct semaphore (16 bytes). | This field may be incorrectly initialized or accessed by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_lock_state 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 init_caps 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 so_delegreturn_mutex has been changed from 20 bytes to 24 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 fc_slot_table has been changed from 304 bytes to 308 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 bc_slot_table has been changed from 304 bytes to 308 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 lock_context has been changed from 24 bytes to 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 | Size of field backing_dev_info has been changed from 380 bytes to 396 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 lockowner_id has been changed from 28 bytes to 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. |
| 3 | Size of field openowner_id has been changed from 28 bytes to 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 | Size of field args has been changed from 40 bytes to 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 | Size of field rpc_data has been changed from 424 bytes to 440 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 stateid 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 args has been changed from 48 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 | Size of field rpc_data has been changed from 448 bytes to 464 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 stateid 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 mutex has been changed from 20 bytes to 24 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 sklist_lock has been changed from 20 bytes to 24 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 224 bytes to 228 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 msi_cap 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 msix_cap 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 dev has been changed from 224 bytes to 228 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 | Type of field pm_cap has been changed from int (4 bytes) to u8 (1 byte). | 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 224 bytes to 228 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 224 bytes to 228 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 open_mutex has been changed from 20 bytes to 24 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 streams 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 oss has been changed from 96 bytes to 100 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 oss has been changed from 28 bytes to 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 | Size of field params_lock has been changed from 20 bytes to 24 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 setup_mutex has been changed from 20 bytes to 24 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 event_constraints has been changed from 2048 bytes to 2304 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 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. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field unnamed0 has been changed from 76 bytes to 80 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field regs has been changed from struct er_account[3] (72 bytes) to struct er_account[4] (96 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 ctx has been changed from 144 bytes to 148 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 hw has been changed from 144 bytes to 152 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 child_mutex has been changed from 20 bytes to 24 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 | Size of field mmap_mutex has been changed from 20 bytes to 24 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 mutex has been changed from 20 bytes to 24 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 data_src 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 cpu_events 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 event_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 | Size of field unconstrainted has been changed from 32 bytes to 36 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 224 bytes to 228 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 mdio_lock has been changed from 20 bytes to 24 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 224 bytes to 228 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 lock has been changed from 20 bytes to 24 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 get_wol 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 set_wol 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 set_vbus 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 proc_self 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 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 | Field files 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 224 bytes to 228 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 224 bytes to 228 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 224 bytes to 228 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 224 bytes to 228 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 t_hash 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 num_supplies 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 supplied_from 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 count has been changed from 13 to 12. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field x86_capability has been changed from __u32[10] (40 bytes) to __u32[11] (44 bytes). | This field may be incorrectly initialized or accessed by applications. |
| 2 | Field coma_bug has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field f00f_bug has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 4 | Field fdiv_bug has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field ps2dev has been changed from 52 bytes to 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 | Size of field tsevq_mux has been changed from 20 bytes to 24 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 dq_lock has been changed from 20 bytes to 24 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 dqio_mutex has been changed from 20 bytes to 24 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 dqonoff_mutex has been changed from 20 bytes to 24 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 need_future_gp 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 abbr 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 barrier_mutex has been changed from 20 bytes to 24 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 | Size of field node has been changed from 128 bytes to 192 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 onoff_mutex has been changed from 20 bytes to 24 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 | Value of member NUM_RFKILL_TYPES 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 | Size of field mutex has been changed from 20 bytes to 24 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 224 bytes to 228 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 ops_lock has been changed from 20 bytes to 24 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 piter has been changed from 20 bytes to 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 | Field linklayer 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 nohz_idle 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 audit_tty_log_passwd 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 posix_timer_id 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 cred_guard_mutex has been changed from 20 bytes to 24 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 perf_event_mutex has been changed from 20 bytes to 24 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 sdev_dev has been changed from 224 bytes to 228 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 224 bytes to 228 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 224 bytes to 228 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 scan_mutex has been changed from 20 bytes to 24 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_dev has been changed from 224 bytes to 228 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 | Size of field shost_gendev has been changed from 224 bytes to 228 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 write_info 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 sem_pending 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 pending_alter 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 sem_otime 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 ports_mutex has been changed from 20 bytes to 24 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 lock has been changed from 20 bytes to 24 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 timer_mutex has been changed from 20 bytes to 24 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 168 bytes to 176 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field dev has been changed from 224 bytes to 228 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 drv_mutex has been changed from 20 bytes to 24 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 vlan_proto 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 inner_mac_header 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 params has been changed from 156 bytes to 180 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 mibs has been changed from unsigned long[27] (108 bytes) to unsigned long[28] (112 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[5] (20 bytes) to unsigned long[6] (24 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from atomic_long_t[5] (20 bytes) to atomic_long_t[6] (24 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from u64[31] (248 bytes) to u64[32] (256 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 mibs has been changed from unsigned long[92] (368 bytes) to unsigned long[95] (380 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[15] (60 bytes) to unsigned long[16] (64 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[7] (28 bytes) to unsigned long[8] (32 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 sk_pacing_rate 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 opos 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 224 bytes to 228 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 ops_mutex has been changed from 20 bytes to 24 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 | Size of field skt_mutex has been changed from 20 bytes to 24 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 mtx has been changed from 20 bytes to 24 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 ampdu_mlme has been changed from 320 bytes to 324 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 sta has been changed from 72 bytes to 76 bytes. | 1) Size of the inclusive type has been changed. 2) Previous accesses of applications and library functions to this field may be broken. |
| 3 | Type of field rx_bytes has been changed from unsigned long (4 bytes) to u64 (8 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 | Type of field tx_bytes has been changed from unsigned long (4 bytes) to u64[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. |
| 5 | Type of field tx_packets has been changed from unsigned long (4 bytes) to u64[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. |
| 6 | The relative position of field tx_bytes has been changed from 36 to 37. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field tx_fragments has been changed from 37 to 35. | Applications will access incorrect memory when attempting to access this field. |
| 8 | The relative position of field tx_packets has been changed from 35 to 36. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field xpt_mutex has been changed from 20 bytes to 24 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 cookie_in_always has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 2 | Field cookie_out_never has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 3 | Field cookie_plus has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field inet_conn has been changed from 824 bytes to 828 bytes. | 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 unused has been changed from 1 bit to 1 byte. | Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken. |
| 3 | Field tlp_high_seq 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. |
| 4 | The relative position of field nonagle has been changed from 23 to 24. | Applications will access incorrect memory when attempting to access this field. |
| 5 | The relative position of field repair has been changed from 26 to 27. | Applications will access incorrect memory when attempting to access this field. |
| 6 | The relative position of field thin_dupack has been changed from 25 to 26. | Applications will access incorrect memory when attempting to access this field. |
| 7 | The relative position of field thin_lto has been changed from 24 to 25. | Applications will access incorrect memory when attempting to access this field. |
| 8 | Field cookie_values has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| 9 | Field early_retrans_delayed 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. |
| 10 | Field frto_counter 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. |
| 11 | Field frto_highmark 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 device has been changed from 224 bytes to 228 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 lock has been changed from 20 bytes to 24 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 owner 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 224 bytes to 228 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 idr has been changed from 24 bytes to 28 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 | Size of field lock has been changed from 20 bytes to 24 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 fast_mode 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 clock_id 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 current_trace 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 dir 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 event_dir 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 events 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 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. |
| 7 | Field 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. |
| 8 | Field options 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 percpu_dir 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 start_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. |
| 11 | Field stop_count 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 systems 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 trace_buffer 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 trace_cpu 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 data 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 trace_cpu 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 allocated_snapshot 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. |
| 2 | Field use_max_tr 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 mutex has been changed from 20 bytes to 24 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 buf_mutex has been changed from 20 bytes to 24 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 flow_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. |
| 2 | Size of field legacy_mutex has been changed from 20 bytes to 24 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 | Size of field termios_mutex has been changed from 20 bytes to 24 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 atomic_write_lock has been changed from 20 bytes to 24 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 ldisc_mutex has been changed from 20 bytes to 24 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. |
| 6 | Field warned has been removed from this type. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field mutex has been changed from 20 bytes to 24 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_mutex has been changed from 20 bytes to 24 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 224 bytes to 228 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 224 bytes to 228 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 level 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 224 bytes to 228 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 refcnt 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 manager_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 | Field manager_arb 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 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. |
| 4 | Field worker_idr 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 refcnt 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 node 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 hash_node 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 maydays 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 pwqs 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 unbound_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. |
| 4 | Field wq_dev 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 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. |
| 6 | Field dfl_pwq 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 | Type of field name has been changed from char[] (4 bytes) to char[24] (24 bytes). | 1) This field may be incorrectly initialized or accessed by applications. 2) Size of the inclusive type has been changed. |
| 8 | The relative position of field rescuer 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. |
| 9 | The relative position of field work_color 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. |
| 10 | The relative position of field flusher_queue 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. |
| 11 | The relative position of field list has been changed from 1 to 0. | 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 name has been changed from 11 to 10. | Applications will access incorrect memory when attempting to access this field. |
| 13 | The relative position of field first_flusher has been changed from 5 to 4. | Applications will access incorrect memory when attempting to access this field. |
| 14 | The relative position of field nr_drainers has been changed from 9 to 8. | Applications will access incorrect memory when attempting to access this field. |
| 15 | The relative position of field flusher_overflow has been changed from 7 to 6. | Applications will access incorrect memory when attempting to access this field. |
| 16 | The relative position of field flush_color has been changed from 3 to 2. | Applications will access incorrect memory when attempting to access this field. |
| 17 | The relative position of field flags has been changed from 0 to 11. | Applications will access incorrect memory when attempting to access this field. |
| 18 | The relative position of field nr_pwqs_to_flush has been changed from 4 to 3. | Applications will access incorrect memory when attempting to access this field. |
| 19 | The relative position of field saved_max_active has been changed from 10 to 9. | Applications will access incorrect memory when attempting to access this field. |
| Change | Effect | |
|---|---|---|
| 1 | Field desc_valid 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 desc 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 props has been changed from 36 bytes to 40 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 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 | The parameter req became passed on stack instead of eax 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 | Type of this global data has been changed from struct pci_device_id[5] const (140 bytes) to struct pci_device_id[7] const (196 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 140 bytes to 196 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter type of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter loginuid has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 7th parameter sessionid has been removed from the calling stack. | This parameter will be ignored by the function. |
| 3 | 8th parameter sid has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 40 bytes to 48 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 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 28 bytes to 32 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 | The parameter bus became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter groups became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter subsys became passed in eax 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 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 316 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter css became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter task has been changed from struct task_struct (1284 bytes) to struct cgroup (180 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Type of 1st parameter cgrp has been changed from struct cgroup const* to struct cgroup* (became non-const). | This function may change parameter cgrp, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications. |
| 3 | Type of return value has been changed from int (4 bytes) to bool (1 byte). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter buflen became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter cgrp became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter css became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter css became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter clnt became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter card became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter id became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter card became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter numid became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gid of type kgid_t* 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter dbs_data has been changed from struct dbs_data (56 bytes) to struct cpufreq_policy (140 bytes). | This parameter may be incorrectly initialized by applications. |
| 2 | Base type of 2nd parameter policy has been changed from struct cpufreq_policy (136 bytes) to struct common_dbs_data (44 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter io_busy of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter drv became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter next_state became passed in ecx 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter init of type void(*)(void*) has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | Parameter release of type void(*)(void*) has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buf became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter size became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter user_data became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter st became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fb became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter to_match became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mode1 became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mode2 became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter prime_fpriv became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter master became passed on stack instead of eax 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 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 9 bytes to 8 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data_len of type u32 has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter nowtime became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ctx became passed on stack instead of eax 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 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 840 bytes to 844 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 840 bytes to 844 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter mode became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter name became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter parent became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter name became passed in eax 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 obj has been changed from struct xdr_netobj (8 bytes) to struct rpcsec_gss_oid (36 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter pseudoflavor became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter hcd became passed on stack instead of eax 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 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter msg became passed on stack instead of edx register. | 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 16 bytes to 20 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_priv became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mask became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter pipe became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter dev_priv became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mask became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter pipe became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter sk became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter uaddr became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter inode became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter de became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sb became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter plane 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of 2nd parameter key has been decreased from 1 to 0. | The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications. NOTE: if this is out-parameter then this change may cause a crash of applications. |
| 2 | Base type of 1st parameter local has been changed from struct ieee80211_local (3776 bytes) to struct ieee80211_key (456 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter kobj became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dying has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type unsigned long has been added to the calling stack. | This parameter will not be initialized by old clients. |
| 2 | The parameter mm became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter tlb became passed on stack instead of eax 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 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 10th parameter use_mfp has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 11th parameter crypt has been removed from the calling stack. | This parameter will be ignored by the function. |
| 3 | 12th parameter assoc_flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| 4 | 13th parameter ht_capa has been removed from the calling stack. | This parameter will be ignored by the function. |
| 5 | 14th parameter ht_capa_mask has been removed from the calling stack. | This parameter will be ignored by the function. |
| 6 | 8th parameter ie has been removed from the calling stack. | This parameter will be ignored by the function. |
| 7 | 9th parameter ie_len has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 10th parameter use_mfp has been removed from the calling stack. | This parameter will be ignored by the function. |
| 2 | 11th parameter crypt has been removed from the calling stack. | This parameter will be ignored by the function. |
| 3 | 12th parameter assoc_flags has been removed from the calling stack. | This parameter will be ignored by the function. |
| 4 | 13th parameter ht_capa has been removed from the calling stack. | This parameter will be ignored by the function. |
| 5 | 14th parameter ht_capa_mask has been removed from the calling stack. | This parameter will be ignored by the function. |
| 6 | 8th parameter ie has been removed from the calling stack. | This parameter will be ignored by the function. |
| 7 | 9th parameter ie_len has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter dentry has been changed from struct dentry (128 bytes) to struct mountpoint (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ns became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter kill has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter stateid of type nfs4_stateid const* 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct event_constraint[11] (352 bytes) to struct event_constraint[12] (432 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 352 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct event_constraint[11] (352 bytes) to struct event_constraint[12] (432 bytes). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 352 bytes to 432 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 236 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter inode has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter inode has been changed from struct inode (328 bytes) to struct pipe_inode_info (88 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 2nd parameter dest_dentry has been changed from struct dentry (128 bytes) to struct mountpoint (16 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 280 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 129 bytes to 131 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 632 bytes to 784 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev 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 | 1st parameter dev has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter root_irq_dir has been removed from the calling stack. | This parameter will be ignored by the function. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 128 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 128 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 448 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 128 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 128 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 448 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter buffer became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter len became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter sdev became passed in eax 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 20 bytes to 12 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 168 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 544 bytes to 548 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 49 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 50 | Size of this global data has been changed from 280 bytes to 296 bytes. | Applications will obtain a different value and execution may change. |
| 51 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 52 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 53 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 54 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 55 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 56 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 57 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 58 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 59 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 60 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 61 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 62 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 63 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 64 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 65 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 66 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 67 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 68 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 69 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 70 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 71 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 72 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 73 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 74 | Size of this global data has been changed from 420 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 75 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 76 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 77 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 78 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 79 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 80 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 81 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 82 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 83 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 84 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 85 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 86 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 87 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 88 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 89 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 90 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 91 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 92 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 93 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 94 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 95 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 96 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 97 | Size of this global data has been changed from 544 bytes to 548 bytes. | Applications will obtain a different value and execution may change. |
| 98 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 99 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 100 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 101 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 102 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 103 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 104 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 105 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 106 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 107 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 108 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 109 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 110 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 111 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 112 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 113 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 114 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 115 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 116 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 117 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 118 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 119 | Size of this global data has been changed from 280 bytes to 296 bytes. | Applications will obtain a different value and execution may change. |
| 120 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 121 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 122 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 123 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 124 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 125 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 126 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 127 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 128 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 129 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 130 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 131 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 132 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 133 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 134 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 135 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 136 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 137 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 138 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 139 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 140 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 141 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 142 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 143 | Size of this global data has been changed from 420 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 144 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 145 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 146 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 147 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 148 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 149 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 150 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 151 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 152 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 153 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 154 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 155 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 156 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 157 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 158 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 159 | Size of this global data has been changed from 280 bytes to 296 bytes. | Applications will obtain a different value and execution may change. |
| 160 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 161 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 162 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 163 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 164 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 165 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 166 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 167 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 168 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 169 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 170 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 171 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 172 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 173 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 174 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 175 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 176 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 177 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 178 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 179 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 180 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 181 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 182 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 183 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 184 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 185 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 186 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 187 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 188 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 189 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 190 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 191 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 192 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 193 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 194 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 195 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 196 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 197 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 198 | Size of this global data has been changed from 544 bytes to 548 bytes. | Applications will obtain a different value and execution may change. |
| 199 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 200 | Size of this global data has been changed from 420 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 201 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 202 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 203 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 204 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 205 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 206 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 207 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 208 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 209 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 210 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 211 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 212 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 213 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 214 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 215 | Size of this global data has been changed from 280 bytes to 296 bytes. | Applications will obtain a different value and execution may change. |
| 216 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 217 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 218 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 219 | Size of this global data has been changed from 544 bytes to 548 bytes. | Applications will obtain a different value and execution may change. |
| 220 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 221 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 222 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 223 | Size of this global data has been changed from 420 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 224 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 225 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 226 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 227 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 228 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 229 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 230 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 231 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 232 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 233 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 234 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 235 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 236 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 237 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 238 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 239 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 240 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 241 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 242 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 243 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 244 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 245 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 246 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 247 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 248 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 249 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 250 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 251 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 252 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 253 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 254 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 255 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 256 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 257 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 258 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 259 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 260 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 261 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 262 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 263 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 264 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 265 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 266 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 267 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 268 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 269 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 270 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 271 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 272 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 273 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 274 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 275 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 276 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 277 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 278 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 279 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 280 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 281 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 282 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 283 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 284 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 285 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 286 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 287 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 288 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 289 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 290 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 291 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 292 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 293 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 294 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 295 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 296 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 297 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 298 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 299 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 300 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 301 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 302 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 303 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 304 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 305 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 306 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 307 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 308 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 309 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 310 | Size of this global data has been changed from 828 bytes to 820 bytes. | Applications will obtain a different value and execution may change. |
| 311 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 312 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 313 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 314 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 315 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 316 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 317 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 318 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 319 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 320 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 321 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 322 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 323 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 324 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 325 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 326 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 327 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 328 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 329 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 330 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 331 | Size of this global data has been changed from 108 bytes to 112 bytes. | Applications will obtain a different value and execution may change. |
| 332 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 333 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 334 | Size of this global data has been changed from 368 bytes to 380 bytes. | Applications will obtain a different value and execution may change. |
| 335 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 336 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 337 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 338 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 339 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 340 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 341 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 342 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 343 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 344 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 345 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 346 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 347 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 348 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 349 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 350 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 351 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 352 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 353 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 354 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 355 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 356 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 357 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 358 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 359 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 360 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 361 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 362 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 363 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 364 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 365 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 366 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 367 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 368 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 369 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 370 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 371 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 372 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 373 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 374 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 375 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 376 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 377 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 378 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 379 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 380 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 381 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 382 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 383 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 384 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 385 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 386 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 387 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 388 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 389 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 390 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 391 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 392 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 393 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 394 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 395 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 396 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 397 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 398 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 399 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 400 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 401 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 402 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 403 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 404 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 405 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 406 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 407 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 408 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 409 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 410 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 411 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 412 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 413 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 414 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 415 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 416 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 417 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 418 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 419 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 420 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 421 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 422 | Size of this global data has been changed from 544 bytes to 548 bytes. | Applications will obtain a different value and execution may change. |
| 423 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 424 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 425 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 426 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 427 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 428 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 429 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 430 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 431 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 432 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 433 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 434 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 435 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 436 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 437 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 438 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 439 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 440 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 441 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 442 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 443 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 444 | Size of this global data has been changed from 280 bytes to 296 bytes. | Applications will obtain a different value and execution may change. |
| 445 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 446 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 447 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 448 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 449 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 450 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 451 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 452 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 453 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 454 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 455 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 456 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 457 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 458 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 459 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 460 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 461 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 462 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 463 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 464 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 465 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 466 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 467 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 468 | Size of this global data has been changed from 420 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 469 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 470 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 471 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 472 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 473 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 474 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 475 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 476 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 477 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 478 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 479 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 480 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 481 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 482 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 483 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 484 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 485 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 486 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 487 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 488 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 489 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 490 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 491 | Size of this global data has been changed from 544 bytes to 548 bytes. | Applications will obtain a different value and execution may change. |
| 492 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 493 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 494 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 495 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 496 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 497 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 498 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 499 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 500 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 501 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 502 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 503 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 504 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 505 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 506 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 507 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 508 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 509 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 510 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 511 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 512 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 513 | Size of this global data has been changed from 280 bytes to 296 bytes. | Applications will obtain a different value and execution may change. |
| 514 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 515 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 516 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 517 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 518 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 519 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 520 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 521 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 522 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 523 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 524 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 525 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 526 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 527 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 528 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 529 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 530 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 531 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 532 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 533 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 534 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 535 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 536 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 537 | Size of this global data has been changed from 420 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 538 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 539 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 540 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 541 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 542 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 543 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 544 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 545 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 546 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 547 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 548 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 549 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 550 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 551 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 552 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 553 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 554 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 555 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 556 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 557 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 558 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 559 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 560 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 561 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 562 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 563 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 564 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 565 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 566 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 567 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 568 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 569 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 570 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 571 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 572 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 573 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 574 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 575 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 576 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 577 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 578 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 579 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 580 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 581 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 582 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 583 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 584 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 585 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 586 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 587 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 588 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 589 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 590 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 591 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 592 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 593 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 594 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 595 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 596 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 597 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 598 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 599 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 600 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 601 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 602 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 603 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 604 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 605 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 606 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 607 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 608 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 609 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 610 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 611 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 612 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 613 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 614 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 615 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 616 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 617 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 618 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 619 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 620 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 621 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 622 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 623 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 624 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 625 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 626 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 627 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 628 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 629 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 630 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 631 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 632 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 633 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 634 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 635 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 636 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 637 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 638 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 639 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 640 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 641 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 642 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 643 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 644 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 645 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 646 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 647 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 648 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 649 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 650 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 651 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 652 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 653 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 654 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 655 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 656 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 657 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 658 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 659 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 660 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 661 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 662 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 663 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 664 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 665 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 666 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 667 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 668 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 669 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 670 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 671 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 672 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 673 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 674 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 675 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 676 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 677 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 678 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 679 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 680 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 681 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 682 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 683 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 684 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 685 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 686 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 687 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 688 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 689 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 690 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 691 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 692 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 693 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 694 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 695 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 696 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 697 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 698 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 699 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 700 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 701 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 702 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 703 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 704 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 705 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 706 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 707 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 708 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 709 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 710 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 711 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 712 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 713 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 714 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 715 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 716 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 717 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 718 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 719 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 720 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 721 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 722 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 723 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 724 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 725 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 726 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 727 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 728 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 729 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 730 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 731 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 732 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 733 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 734 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 735 | Size of this global data has been changed from 544 bytes to 548 bytes. | Applications will obtain a different value and execution may change. |
| 736 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 737 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 738 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 739 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 740 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 741 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 742 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 743 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 744 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 745 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 746 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 747 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 748 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 749 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 750 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 751 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 752 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 753 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 754 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 755 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 756 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 757 | Size of this global data has been changed from 280 bytes to 296 bytes. | Applications will obtain a different value and execution may change. |
| 758 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 759 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 760 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 761 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 762 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 763 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 764 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 765 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 766 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 767 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 768 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 769 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 770 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 771 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 772 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 773 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 774 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 775 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 776 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 777 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 778 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 779 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 780 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 781 | Size of this global data has been changed from 420 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 782 | Size of this global data has been changed from 2496 bytes to 2560 bytes. | Applications will obtain a different value and execution may change. |
| 783 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 784 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 785 | Size of this global data has been changed from 692 bytes to 700 bytes. | Applications will obtain a different value and execution may change. |
| 786 | Size of this global data has been changed from 304 bytes to 308 bytes. | Applications will obtain a different value and execution may change. |
| 787 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 788 | Size of this global data has been changed from 156 bytes to 160 bytes. | Applications will obtain a different value and execution may change. |
| 789 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 790 | Size of this global data has been changed from 912 bytes to 936 bytes. | Applications will obtain a different value and execution may change. |
| 791 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 792 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 793 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 794 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 795 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 796 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 797 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 798 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 799 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 800 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 801 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 802 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 803 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 804 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 805 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 806 | Size of this global data has been changed from 280 bytes to 296 bytes. | Applications will obtain a different value and execution may change. |
| 807 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 808 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 809 | Size of this global data has been changed from 172 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 810 | Size of this global data has been changed from 28 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 811 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 812 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 813 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 814 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 815 | Size of this global data has been changed from 328 bytes to 336 bytes. | Applications will obtain a different value and execution may change. |
| 816 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 817 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 818 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 819 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 820 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 821 | Size of this global data has been changed from 420 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 822 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 823 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 824 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 825 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 826 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 827 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 828 | Size of this global data has been changed from 84 bytes to 76 bytes. | Applications will obtain a different value and execution may change. |
| 829 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 830 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 831 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 832 | Size of this global data has been changed from 576 bytes to 640 bytes. | Applications will obtain a different value and execution may change. |
| 833 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 834 | Size of this global data has been changed from 544 bytes to 548 bytes. | Applications will obtain a different value and execution may change. |
| 835 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 836 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 837 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 838 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 839 | Size of this global data has been changed from 472 bytes to 476 bytes. | Applications will obtain a different value and execution may change. |
| 840 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 841 | Size of this global data has been changed from 252 bytes to 260 bytes. | Applications will obtain a different value and execution may change. |
| 842 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 843 | Size of this global data has been changed from 40 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 844 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 845 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 846 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 847 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 848 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 849 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 850 | Size of this global data has been changed from 36 bytes to 40 bytes. | Applications will obtain a different value and execution may change. |
| 851 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 852 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 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 | The parameter mntroot became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter mount_info became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter s became passed on stack instead of eax 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 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter list of type struct list_head* 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter set_ssthresh became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter sk became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter addr became passed on stack instead of edx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter family became passed on stack instead of ecx register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter sk became passed on stack instead of eax register. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter bc became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter offs_tai of type ktime_t* 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 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter fmt became passed in ecx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 2 | The parameter ip became passed in edx register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| 3 | The parameter tr became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter skip of type int has been added to the calling stack. | This parameter will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tr has been changed from struct trace_array (56 bytes) to struct trace_buffer (24 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter tr has been changed from struct trace_array (56 bytes) to struct trace_buffer (24 bytes). | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 int (4 bytes) to bool (1 byte). | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 4 bytes to 1 byte. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter system has been changed from struct event_subsystem to struct ftrace_subsystem_dir of different format. | This parameter may be incorrectly initialized by applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this global data has been changed from 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter tty became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter ld became passed in eax register instead of stack. | Violation of the calling convention. This may result in crash or incorrect behavior of applications. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter port became passed in eax 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 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | The parameter urb became passed on stack instead of eax 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 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 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 7176 bytes to 7224 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from char (1 byte) to struct acpi_exception_info (4 bytes). | Applications will obtain a different return value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter func of type void(*)(struct callback_head*) 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 32 bytes to 36 bytes. | Applications will obtain a different value and execution may change. |
| 2 | Size of this global data has been changed from 416 bytes to 424 bytes. | Applications will obtain a different value and execution may change. |
| 3 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 4 | Size of this global data has been changed from 640 bytes to 660 bytes. | Applications will obtain a different value and execution may change. |
| 5 | Size of this global data has been changed from 132 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 6 | Size of this global data has been changed from 212 bytes to 216 bytes. | Applications will obtain a different value and execution may change. |
| 7 | Size of this global data has been changed from 28 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| 8 | Size of this global data has been changed from 68 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 9 | Size of this global data has been changed from 400 bytes to 404 bytes. | Applications will obtain a different value and execution may change. |
| 10 | Size of this global data has been changed from 324 bytes to 328 bytes. | Applications will obtain a different value and execution may change. |
| 11 | Size of this global data has been changed from 512 bytes to 576 bytes. | Applications will obtain a different value and execution may change. |
| 12 | Size of this global data has been changed from 128 bytes to 132 bytes. | Applications will obtain a different value and execution may change. |
| 13 | Size of this global data has been changed from 16 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 14 | Size of this global data has been changed from 300 bytes to 304 bytes. | Applications will obtain a different value and execution may change. |
| 15 | Size of this global data has been changed from 92 bytes to 256 bytes. | Applications will obtain a different value and execution may change. |
| 16 | Size of this global data has been changed from 84 bytes to 192 bytes. | Applications will obtain a different value and execution may change. |
| 17 | Size of this global data has been changed from 1168 bytes to 1188 bytes. | Applications will obtain a different value and execution may change. |
| 18 | Size of this global data has been changed from 24 bytes to 28 bytes. | Applications will obtain a different value and execution may change. |
| 19 | Size of this global data has been changed from 52 bytes to 56 bytes. | Applications will obtain a different value and execution may change. |
| 20 | Size of this global data has been changed from 272 bytes to 284 bytes. | Applications will obtain a different value and execution may change. |
| 21 | Size of this global data has been changed from 136 bytes to 140 bytes. | Applications will obtain a different value and execution may change. |
| 22 | Size of this global data has been changed from 100 bytes to 116 bytes. | Applications will obtain a different value and execution may change. |
| 23 | Size of this global data has been changed from 92 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 24 | Size of this global data has been changed from 60 bytes to 64 bytes. | Applications will obtain a different value and execution may change. |
| 25 | Size of this global data has been changed from 4412 bytes to 4420 bytes. | Applications will obtain a different value and execution may change. |
| 26 | Size of this global data has been changed from 192 bytes to 240 bytes. | Applications will obtain a different value and execution may change. |
| 27 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 28 | Size of this global data has been changed from 240 bytes to 244 bytes. | Applications will obtain a different value and execution may change. |
| 29 | Size of this global data has been changed from 28 bytes to 32 bytes. | Applications will obtain a different value and execution may change. |
| 30 | Size of this global data has been changed from 80 bytes to 84 bytes. | Applications will obtain a different value and execution may change. |
| 31 | Size of this global data has been changed from 216 bytes to 220 bytes. | Applications will obtain a different value and execution may change. |
| 32 | Size of this global data has been changed from 624 bytes to 636 bytes. | Applications will obtain a different value and execution may change. |
| 33 | Size of this global data has been changed from 168 bytes to 176 bytes. | Applications will obtain a different value and execution may change. |
| 34 | Size of this global data has been changed from 400 bytes to 420 bytes. | Applications will obtain a different value and execution may change. |
| 35 | Size of this global data has been changed from 44 bytes to 48 bytes. | Applications will obtain a different value and execution may change. |
| 36 | Size of this global data has been changed from 380 bytes to 396 bytes. | Applications will obtain a different value and execution may change. |
| 37 | Size of this global data has been changed from 64 bytes to 88 bytes. | Applications will obtain a different value and execution may change. |
| 38 | Size of this global data has been changed from 1284 bytes to 1288 bytes. | Applications will obtain a different value and execution may change. |
| 39 | Size of this global data has been changed from 224 bytes to 228 bytes. | Applications will obtain a different value and execution may change. |
| 40 | Size of this global data has been changed from 144 bytes to 152 bytes. | Applications will obtain a different value and execution may change. |
| 41 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 42 | Size of this global data has been changed from 76 bytes to 80 bytes. | Applications will obtain a different value and execution may change. |
| 43 | Size of this global data has been changed from 144 bytes to 148 bytes. | Applications will obtain a different value and execution may change. |
| 44 | Size of this global data has been changed from 176 bytes to 180 bytes. | Applications will obtain a different value and execution may change. |
| 45 | Size of this global data has been changed from 144 bytes to 172 bytes. | Applications will obtain a different value and execution may change. |
| 46 | Size of this global data has been changed from 64 bytes to 96 bytes. | Applications will obtain a different value and execution may change. |
| 47 | Size of this global data has been changed from 568 bytes to 584 bytes. | Applications will obtain a different value and execution may change. |
| 48 | Size of this global data has been changed from 20 bytes to 24 bytes. | Applications will obtain a different value and execution may change. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 6 bytes to 7 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 6 bytes to 7 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field reserved has been changed from u8 (1 byte) to u16 (2 bytes). | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Field reserved has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 6 bytes to 7 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 6 bytes to 7 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field reserved has been changed from u8 (1 byte) to u16 (2 bytes). | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 24 bytes to 28 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 6 bytes to 7 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 588 bytes to 600 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 92 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 | Field hotplug 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 20 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 36 bytes to 40 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 92 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field ki_cancel has been changed from int(*)(struct kiocb*, struct io_event*) to int()(struct kiocb*, struct io_event*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field internal_pages 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 rcu_work 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 unnamed0 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 4 | Field unnamed1 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 5 | Field unnamed2 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 6 | Field unnamed3 has been added to this type. | Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 7 | Size of this type has been changed from 208 bytes to 448 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 8 | Field reqs_active has been renamed to mmap_size. | 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 20 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 640 bytes to 660 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 76 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 flavor2info 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 info2flavor 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 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 124 bytes to 132 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 380 bytes to 396 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 100 bytes to 116 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 304 bytes to 316 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 212 bytes to 216 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rescue_workqueue 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 rescue_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. |
| 3 | Field rescue_work 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 rescue_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 16 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 release has been changed from int(*)(struct gendisk*, fmode_t) to void(*)(struct gendisk*, fmode_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 1168 bytes to 1188 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_capa 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 vht_capa_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. |
| 3 | Size of this type has been changed from 128 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 | Field vht_capa 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 vht_capa_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. |
| 3 | Size of this type has been changed from 156 bytes to 180 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field crit_proto_start 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 crit_proto_stop 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 update_ft_ies 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 | Size of this type has been changed from 316 bytes to 328 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 188 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 | Size of this type has been changed from 4412 bytes to 4420 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client 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 176 bytes to 180 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 idr has been changed from 24 bytes to 28 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 508 bytes to 516 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 412 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 800 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 528 bytes to 532 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 232 bytes to 236 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field have_governor_per_policy 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 136 bytes to 140 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 136 bytes to 140 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 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field attr_group has been renamed to usage_count. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| 3 | Field governor has been renamed to cdata. | 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 304 bytes to 360 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 784 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field en_core_tk_irqen has been renamed to bctimer. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_key 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 224 bytes to 228 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 devnode has been changed from char*(*)(struct device*, umode_t*) to char*(*)(struct device*, umode_t*, kuid_t*, kgid_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 324 bytes to 332 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field exp_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 | Field list_node 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 52 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 864 bytes to 860 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 788 bytes to 792 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 368 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field initial_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 | Size of this type has been changed from 12 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 960 bytes to 992 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 160 bytes to 172 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field info_ent 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 info_ent has been changed from struct drm_info_list* to struct drm_info_list const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 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 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 324 bytes to 332 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 bytes to 32 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 344 bytes to 348 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 116 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 28 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 | Size of this type has been changed from 2000 bytes to 2004 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 324 bytes to 328 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int()(struct request_queue*) to int()(struct request_queue*, struct elevator_type*). | 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 232 bytes to 236 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 604 bytes to 612 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 552 bytes to 36 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 20 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 36 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 2244 bytes to 2280 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field skip_vt_switch 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 608 bytes to 620 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Value of member FIX_BTMAP_END has been changed from 233 to 234. | Applications may execute a wrong branch of code in the library and therefore change the behavior. |
| 2 | Value of member FIX_KMAP_END has been changed from 229 to 230. | 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 92 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 132 bytes to 140 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 328 bytes to 336 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 640 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 132 bytes to 140 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 idr has been changed from 24 bytes to 28 bytes. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field files 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 | Type of field flags has been changed from unsigned int to int. | 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 8308 bytes to 8316 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 72 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field parallel_ops 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 128 bytes to 132 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 404 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 300 bytes to 304 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 68 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 gss_import_sec_context has been changed from int(*)(void const*, size_t, struct gss_ctx*, gfp_t) to int(*)(void const*, size_t, struct gss_ctx*, time_t*, gfp_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 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 144 bytes to 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_headset_mic has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 8 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field is_headphone_mic 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 84 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field playing 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 220 bytes to 228 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 948 bytes to 964 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 124 bytes to 132 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_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. |
| 2 | Size of this type has been changed from 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 52 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 2588 bytes to 2668 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field hp_mic_jack_modes 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 hp_mic_pin 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 byte2 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 freq 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 24 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 744 bytes to 748 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 3772 bytes to 3800 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idle 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 request 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 wait 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 | Size of this type has been changed from 28 bytes to 40 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 192 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 316 bytes to 324 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 244 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 268 bytes to 272 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus_recovery_info 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 360 bytes to 372 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 268 bytes to 272 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 116 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 76 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field crtc_mode_set has been changed from int(*)(struct drm_crtc*, struct drm_display_mode*, struct drm_display_mode*, int, int, struct drm_framebuffer*) to int(*)(struct drm_crtc*, int, int, struct drm_framebuffer*). | 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 16 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 516 bytes to 656 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 fence_reg has been changed from 5 bits to 6 bits. | Previous accesses of applications and library functions to this field may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 7848 bytes to 8448 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 backlight 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 36 bytes to 40 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 2956 bytes to 3084 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 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 124 bytes to 128 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field hw_max 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 412 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 28 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 | Size of this type has been changed from 28 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 | Size of this type has been changed from 24 bytes to 28 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field variable 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 6 bytes to 1 byte. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ext_chan_switch 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 172 bytes to 168 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field presp has been changed from struct sk_buff (192 bytes) to struct beacon_data (24 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_capa 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 vht_capa_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. |
| 3 | Size of this type has been changed from 476 bytes to 500 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 712 bytes to 716 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 3776 bytes to 2628 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 140 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of field vif has been changed from 176 bytes to 228 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 40 bytes to 44 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 156 bytes to 144 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field timeout_int has been changed from unsigned char (1 byte) to struct ieee80211_timeout_interval_ie (5 bytes). | Possible access of applications to incorrect memory through the pointer. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 712 bytes to 716 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 280 bytes to 296 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 136 bytes to 140 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 828 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 8320 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 556 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 84 bytes to 88 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 76 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 684 bytes to 692 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field polled 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 1628 bytes to 2080 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 676 bytes to 704 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field port_reversal has been renamed to saved_port_bits. | 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 544 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 | Field hpd_pin 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 92 bytes to 104 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sdvox_reg has been renamed to hdmi_reg. | 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 72 bytes to 76 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 60 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 828 bytes to 820 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 52 bytes to 56 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field rw_mutex has been renamed to rwsem. | 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 272 bytes to 284 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ecn 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 dev_addr_genid 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 728 bytes to 736 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 60 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 1360 bytes to 1364 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 60 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 3300 bytes to 3312 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 9536 bytes to 9600 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 52 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 184 bytes to 188 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 404 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field short_preamble 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 use_cts_prot 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 use_rts 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 | Size of this type has been changed from 13 bytes to 14 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 5 | Field skip_table 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 36 bytes to 40 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field p2p_noa_attr 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 152 bytes to 204 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field uapsd_queues 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 104 bytes to 116 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field uapsd_max_sp_len 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 280 bytes to 284 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Base type of field flush has been changed from void(*)(struct ieee80211_hw*, bool) to void(*)(struct ieee80211_hw*, u32, bool). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 3 | Base type of field remain_on_channel has been changed from int(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct ieee80211_channel*, int) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct ieee80211_channel*, int, enum ieee80211_roc_type). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field rates 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 72 bytes to 76 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 10 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 36 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 228 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 104 bytes to 108 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 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 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 | Size of this type has been changed from 1512 bytes to 1516 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 416 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 32 bytes to 36 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 136 bytes to 140 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field spin_mlock 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 20 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 2496 bytes to 2560 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 ndo_vlan_rx_add_vid has been changed from int(*)(struct net_device*, unsigned short) to int(*)(struct net_device*, __be16, u16). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| 2 | Base type of field ndo_vlan_rx_kill_vid has been changed from int(*)(struct net_device*, unsigned short) to int(*)(struct net_device*, __be16, u16). | 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 28 bytes to 12 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 160 bytes to 156 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void()(u_int8_t, unsigned int, struct sk_buff const*, struct net_device const*, struct net_device const*, struct nf_loginfo const*, char const*) to void()(struct net*, u_int8_t, unsigned int, struct sk_buff const*, struct net_device const*, struct net_device const*, struct nf_loginfo const*, char const*). | Replacement of the base data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Field size 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 28 bytes to 36 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 224 bytes to 228 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 692 bytes to 700 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field slot_tbl_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 304 bytes to 308 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field io_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 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 | Size of this type has been changed from 60 bytes to 68 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 912 bytes to 936 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 flavors has been changed from struct nfs4_secinfo_flavor[] to struct nfs4_secinfo4[]. | 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 424 bytes to 440 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 512 bytes to 528 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 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 448 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 548 bytes to 564 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 48 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 | Type of field notifier_call has been changed from int(*)(struct notifier_block*, unsigned long, void*) to notifier_fn_t. | 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 144 bytes to 148 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 28 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 404 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 840 bytes to 844 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 244 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 240 bytes to 244 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 344 bytes to 356 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 648 bytes to 652 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 60 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 96 bytes to 100 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 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 | Size of this type has been changed from 2312 bytes to 2568 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 76 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 flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 32 bytes to 36 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 80 bytes to 104 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 180 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 568 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 | Size of this type has been changed from 144 bytes to 148 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field weight 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 104 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 236 bytes to 244 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 76 bytes to 80 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Size of field unnamed0 has been changed from 76 bytes to 80 bytes. | Size of the inclusive type has been changed. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 120 bytes to 124 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 428 bytes to 436 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 468 bytes to 476 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 140 bytes to 148 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 84 bytes to 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 80 bytes to 84 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 88 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Reserved field __reserved has been replaced by linklayer. | This field will not be initialized by old clients. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 252 bytes to 256 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 324 bytes to 328 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 388 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 280 bytes to 284 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 156 bytes to 164 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 116 bytes to 124 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 84 bytes to 76 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field write_proc has been renamed to in_use. | 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 332 bytes to 336 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 4320 bytes to 4324 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 156 bytes to 160 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 172 bytes to 180 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 192 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field wakeup_work 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 448 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 | Base type of field rtx_syn_ack has been changed from int(*)(struct sock*, struct request_sock*, struct request_values*) to int(*)(struct sock*, struct request_sock*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_work 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 96 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_work 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 144 bytes to 172 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 556 bytes to 564 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int(*)(struct sk_buff*, struct nlmsghdr*, void*) to int(*)(struct sk_buff*, struct nlmsghdr*). | 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 48 bytes to 44 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 20 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 240 bytes to 244 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 624 bytes to 636 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 1284 bytes to 1288 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 bytes to 24 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 676 bytes to 684 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 304 bytes to 308 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 708 bytes to 720 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 172 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Field proc_info has been renamed to show_info. | Renaming of a field in data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field sb_clone_mnt_opts has been changed from void(*)(struct super_block const*, struct super_block*) to int(*)(struct super_block const*, struct super_block*). | Replacement of field base type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field 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. |
| 2 | Field pending_alter 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 pending_const 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 sem_otime 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 16 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field sem_pending has been renamed to pending_const. | 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 176 bytes to 180 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 76 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 152 bytes to 156 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 188 bytes to 196 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 384 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 3 has been changed from PARTIAL_L3 to PARTIAL_NODE. | 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 184 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 108 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 | Size of this type has been changed from 20 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 20 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 252 bytes to 260 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 380 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 60 bytes to 64 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 28 bytes to 32 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 420 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 32 bytes to 36 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 560 bytes to 572 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 320 bytes to 324 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 812 bytes to 880 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 2 | Type of field tx_fragments has been changed from unsigned long to u32. | 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 472 bytes to 476 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field frto 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 296 bytes to 304 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 36 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 | Size of this type has been changed from 444 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 | Size of this type has been changed from 28 bytes to 20 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field type became const. | The value of this field is expected to be const in new library version, but can be modified by old applications. |
| 2 | Field name 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 name has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| 4 | Type of field type has been changed from char* to char const*. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field ref 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 112 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Field cpu has been renamed to name. | 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 76 bytes to 88 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 176 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Size of this type has been changed from 400 bytes to 420 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 44 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 340 bytes to 344 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 596 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 276 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 216 bytes to 220 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 232 bytes to 236 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 | Field mayday_node 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 pwqs_node 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 unbound_release_work 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 92 bytes to 256 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 512 bytes to 576 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| 3 | Type of field cpu has been changed from unsigned int to int. | Replacement of the field data type may indicate a change in the semantic meaning of the field. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_pwqs 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 numa_pwq_tbl 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 84 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 | Size of this type has been changed from 68 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 extra_flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 36 bytes to 40 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 548 bytes. | The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | 1) This field will not be initialized by old clients. 2) Size of the inclusive type has been changed. NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications. |
| 2 | Size of this type has been changed from 28 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 3rd parameter dev has been changed from struct net_device* to struct net_device const*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ptr has been renamed to func. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter ptr has been changed from void()(void*, async_cookie_t) to void(*)(void*, async_cookie_t). | Replacement of parameter base type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ptr has been renamed to func. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Base type of 1st parameter ptr has been changed from void()(void*, async_cookie_t) to void(*)(void*, async_cookie_t). | Replacement of parameter base 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 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 | 2nd parameter task has been renamed to ancestor. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter cgrp has been changed from struct cgroup const* to struct cgroup*. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dbs_data has been renamed to policy. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter policy has been renamed to cdata. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter next_state has been renamed to index. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u32 to rpc_authflavor_t. | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter sdvox_reg has been renamed to hdmi_reg. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to key. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | 2nd parameter key has been renamed to delay_tailroom. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter current_nid has been renamed to page_nid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter macaddr has been renamed to addr. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter dentry has been renamed to mp. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 3rd parameter pid has been changed from u_int32_t to u32. | 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 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 | 1st parameter inode has been renamed to pipe. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter dest_dentry has been renamed to dest_mp. | Renaming of a parameter 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 | 2nd parameter data has been renamed to csd. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tr has been renamed to buf. | Renaming of a parameter may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tr has been renamed to buf. | Renaming of a parameter 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 | 1st parameter system has been renamed to dir. | Renaming of a parameter 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 return value has been changed from void to acpi_status (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter device has been renamed to handle. | Renaming of a parameter may indicate a change in its semantic meaning. |
| 2 | Type of 1st parameter device has been changed from struct acpi_device* to acpi_handle. | 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 struct vc_data* (4 bytes). | Replacement of return type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter cpu has been changed from unsigned int to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter cpu has been changed from unsigned int to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter cpu has been changed from unsigned int to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter cpu has been changed from unsigned int to int. | Replacement of parameter data type may indicate a change in its semantic meaning. |
| Change | Effect | |
|---|---|---|
| 1 | The member FIX_RO_IDT with value 70 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PCH_NOP with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_QUEUE_STOP_REASON_FLUSH with value 7 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member RFKILL_TYPE_NFC with value 8 has been added. | No effect. |
| Module Name | vmlinux |
|---|---|
| Version #1 | 3.9.11 |
| Version #2 | 3.10.19 |
| CPU Type | x86 |
| Subject | Source Compatibility |
| Total Header Files | 790 |
|---|---|
| Total Source Files | 1453 |
| Total Objects | 1 |
| Total Symbols / Types | 16711 / 9220 |
| Verdict | Incompatible (50.7%) |
| Severity | Count | |
|---|---|---|
| Added Symbols | - | 686 |
| Removed Symbols | High | 515 |
| Problems with Data Types | High | 125 |
| Medium | 13 | |
| Low | 248 | |
| Problems with Symbols | High | 25 |
| Medium | 56 | |
| Low | 14 | |
| Problems with Constants | Low | 0 |
| Other Changes in Data Types | - | 194 |
| Other Changes in Symbols | - | 34 |
| Change | Effect | |
|---|---|---|
| 1 | Field param_count has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_name_info' has no member named 'param_count'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus_address has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct acpi_device_flags' has no member named 'bus_address'. |
| Change | Effect | |
|---|---|---|
| 1 | Field ki_batch has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_batch'. |
| 2 | Field ki_flags has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_flags'. |
| 3 | Field ki_key has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_key'. |
| 4 | Field ki_retry has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_retry'. |
| 5 | Field ki_run_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kiocb' has no member named 'ki_run_list'. |
| Change | Effect | |
|---|---|---|
| 1 | Field active_reqs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'active_reqs'. |
| 2 | Field ctx_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'ctx_lock'. |
| 3 | Field mm has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'mm'. |
| 4 | Field ring_info has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'ring_info'. |
| 5 | Field run_list has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'run_list'. |
| 6 | Field wait has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'wait'. |
| 7 | Field wq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct kioctx' has no member named 'wq'. |
| 8 | Field reqs_active has been renamed to mmap_size. | Recompilation of a client program may be broken with the error message: struct kioctx has no member named reqs_active. |
| Change | Effect | |
|---|---|---|
| 1 | Field node has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct async_domain' has no member named 'node'. |
| Change | Effect | |
|---|---|---|
| 1 | Field task has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bdi_writeback' has no member named 'task'. |
| 2 | Field last_active has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bdi_writeback' has no member named 'last_active'. |
| 3 | Field wakeup_timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct bdi_writeback' has no member named 'wakeup_timer'. |
| Change | Effect | |
|---|---|---|
| 1 | Field top_cgroup has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup' has no member named 'top_cgroup'. |
| Change | Effect | |
|---|---|---|
| 1 | Field active has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cgroup_subsys' has no member named 'active'. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_cpu_cdbs has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dbs_data' has no member named 'get_cpu_cdbs'. |
| 2 | Field get_cpu_dbs_info_s has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dbs_data' has no member named 'get_cpu_dbs_info_s'. |
| 3 | Field gov_check_cpu has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dbs_data' has no member named 'gov_check_cpu'. |
| 4 | Field gov_dbs_timer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dbs_data' has no member named 'gov_dbs_timer'. |
| 5 | Field gov_ops has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct dbs_data' has no member named 'gov_ops'. |
| 6 | Field attr_group has been renamed to usage_count. | Recompilation of a client program may be broken with the error message: struct dbs_data has no member named attr_group. |
| 7 | Field governor has been renamed to cdata. | Recompilation of a client program may be broken with the error message: struct dbs_data has no member named governor. |
| Change | Effect | |
|---|---|---|
| 1 | Field en_core_tk_irqen has been renamed to bctimer. | Recompilation of a client program may be broken with the error message: struct cpuidle_driver has no member named en_core_tk_irqen. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_modes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_connector' has no member named 'user_modes'. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_io_pages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext4_io_end' has no member named 'num_io_pages'. |
| 2 | Field pages has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext4_io_end' has no member named 'pages'. |
| Change | Effect | |
|---|---|---|
| 1 | Field io_page has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ext4_io_submit' has no member named 'io_page'. |
| Change | Effect | |
|---|---|---|
| 1 | Field next has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct fdtable' has no member named 'next'. |
| Change | Effect | |
|---|---|---|
| 1 | Field last_wd has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct inotify_group_private_data' has no member named 'last_wd'. |
| Change | Effect | |
|---|---|---|
| 1 | Field dir 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 'dir'. |
| Change | Effect | |
|---|---|---|
| 1 | Field add_in_jack_modes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_gen_spec' has no member named 'add_in_jack_modes'. |
| 2 | Field add_out_jack_modes has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_gen_spec' has no member named 'add_out_jack_modes'. |
| 3 | Field shared_mic_hp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct hda_gen_spec' has no member named 'shared_mic_hp'. |
| Change | Effect | |
|---|---|---|
| 1 | Field max_bitrate has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cea_sad' has no member named 'max_bitrate'. |
| 2 | Field profile has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cea_sad' has no member named 'profile'. |
| 3 | Field rates has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cea_sad' has no member named 'rates'. |
| 4 | Field sample_bits has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cea_sad' has no member named 'sample_bits'. |
| Change | Effect | |
|---|---|---|
| 1 | Field detach_adapter has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct i2c_driver' has no member named 'detach_adapter'. |
| Change | Effect | |
|---|---|---|
| 1 | Field backlight_enabled has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'backlight_enabled'. |
| 2 | Field backlight_level has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'backlight_level'. |
| 3 | Field hotplug_supported_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'hotplug_supported_mask'. |
| 4 | Field num_pipe has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'num_pipe'. |
| 5 | Field pipestat has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct drm_i915_private' has no member named 'pipestat'. |
| Change | Effect | |
|---|---|---|
| 1 | Field element_id has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-ieee80211.h-813' has no member named 'element_id'. |
| 2 | Field length has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-ieee80211.h-813' has no member named 'length'. |
| 3 | Field sw_elem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'anon-struct-ieee80211.h-813' has no member named 'sw_elem'. |
| Change | Effect | |
|---|---|---|
| 1 | Field skb has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ibss' has no member named 'skb'. |
| 2 | Field timer_running has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_ibss' has no member named 'timer_running'. |
| Change | Effect | |
|---|---|---|
| 1 | Field timers_running 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 'timers_running'. |
| Change | Effect | |
|---|---|---|
| 1 | Field timers_running has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_if_mesh' has no member named 'timers_running'. |
| Change | Effect | |
|---|---|---|
| 1 | Field _oper_channel 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 '_oper_channel'. |
| 2 | Field _oper_channel_type 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 '_oper_channel_type'. |
| 3 | Field csa_channel 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 'csa_channel'. |
| 4 | Field napi 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 'napi'. |
| 5 | Field napi_dev 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 'napi_dev'. |
| Change | Effect | |
|---|---|---|
| 1 | Field suspend_bss_conf 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 'suspend_bss_conf'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cf_params has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'cf_params'. |
| 2 | Field cf_params_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'cf_params_len'. |
| 3 | Field ds_params_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'ds_params_len'. |
| 4 | Field erp_info_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'erp_info_len'. |
| 5 | Field fh_params has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'fh_params'. |
| 6 | Field fh_params_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'fh_params_len'. |
| 7 | Field ibss_params has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'ibss_params'. |
| 8 | Field ibss_params_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'ibss_params_len'. |
| 9 | Field num_of_quiet_elem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'num_of_quiet_elem'. |
| 10 | Field quiet_elem has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'quiet_elem'. |
| 11 | Field quiet_elem_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'quiet_elem_len'. |
| 12 | Field timeout_int_len has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee802_11_elems' has no member named 'timeout_int_len'. |
| Change | Effect | |
|---|---|---|
| 1 | Field bpp has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_crtc' has no member named 'bpp'. |
| 2 | Field cpu_transcoder has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct intel_crtc' has no member named 'cpu_transcoder'. |
| Change | Effect | |
|---|---|---|
| 1 | Field port_reversal has been renamed to saved_port_bits. | Recompilation of a client program may be broken with the error message: struct intel_digital_port has no member named port_reversal. |
| Change | Effect | |
|---|---|---|
| 1 | Field sdvox_reg has been renamed to hdmi_reg. | Recompilation of a client program may be broken with the error message: struct intel_hdmi has no member named sdvox_reg. |
| Change | Effect | |
|---|---|---|
| 1 | Field rs_lock has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct netns_ipvs' has no member named 'rs_lock'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rw_mutex has been renamed to rwsem. | Recompilation of a client program may be broken with the error message: struct ipc_ids has no member named rw_mutex. |
| Change | Effect | |
|---|---|---|
| 1 | Field b_cow_tid has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct journal_head' has no member named 'b_cow_tid'. |
| Change | Effect | |
|---|---|---|
| 1 | Field p2p_ctwindow has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss_conf' has no member named 'p2p_ctwindow'. |
| 2 | Field p2p_oppps has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_bss_conf' has no member named 'p2p_oppps'. |
| Change | Effect | |
|---|---|---|
| 1 | Field channel has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_conf' has no member named 'channel'. |
| 2 | Field channel_type has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct ieee80211_conf' has no member named 'channel_type'. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rps_dev_flow_table' has no member named 'free_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Field inode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct pipe_inode_info' has no member named 'inode'. |
| Change | Effect | |
|---|---|---|
| 1 | Field pde_users has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct proc_dir_entry' has no member named 'pde_users'. |
| 2 | Field read_proc has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct proc_dir_entry' has no member named 'read_proc'. |
| 3 | Field write_proc has been renamed to in_use. | Recompilation of a client program may be broken with the error message: struct proc_dir_entry has no member named write_proc. |
| Change | Effect | |
|---|---|---|
| 1 | Field coma_bug has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuinfo_x86' has no member named 'coma_bug'. |
| 2 | Field f00f_bug has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuinfo_x86' has no member named 'f00f_bug'. |
| 3 | Field fdiv_bug has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct cpuinfo_x86' has no member named 'fdiv_bug'. |
| Change | Effect | |
|---|---|---|
| 1 | Field wakemask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct rcu_node' has no member named 'wakemask'. |
| Change | Effect | |
|---|---|---|
| 1 | Field page has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sg_page_iter' has no member named 'page'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cred has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct scm_cookie' has no member named 'cred'. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_info has been renamed to show_info. | Recompilation of a client program may be broken with the error message: struct scsi_host_template has no member named proc_info. |
| Change | Effect | |
|---|---|---|
| 1 | Field sem_pending has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sem' has no member named 'sem_pending'. |
| Change | Effect | |
|---|---|---|
| 1 | Field sem_otime has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct sem_array' has no member named 'sem_otime'. |
| 2 | Field sem_pending has been renamed to pending_const. | Recompilation of a client program may be broken with the error message: struct sem_array has no member named sem_pending. |
| Change | Effect | |
|---|---|---|
| 1 | Name of member with value 3 has been changed from PARTIAL_L3 to PARTIAL_NODE. | Recompilation of a client program may be broken with the error message: 'PARTIAL_L3' was not declared in this scope. |
| Change | Effect | |
|---|---|---|
| 1 | Field cookie_in_always has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_options_received' has no member named 'cookie_in_always'. |
| 2 | Field cookie_out_never has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_options_received' has no member named 'cookie_out_never'. |
| 3 | Field cookie_plus has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_options_received' has no member named 'cookie_plus'. |
| Change | Effect | |
|---|---|---|
| 1 | Field cookie_values has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_sock' has no member named 'cookie_values'. |
| 2 | Field early_retrans_delayed has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_sock' has no member named 'early_retrans_delayed'. |
| 3 | Field frto_counter has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_sock' has no member named 'frto_counter'. |
| 4 | Field frto_highmark has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tcp_sock' has no member named 'frto_highmark'. |
| Change | Effect | |
|---|---|---|
| 1 | Field owner has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct thermal_governor' has no member named 'owner'. |
| Change | Effect | |
|---|---|---|
| 1 | Field fast_mode has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct mmu_gather' has no member named 'fast_mode'. |
| Change | Effect | |
|---|---|---|
| 1 | Field entry has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct event_subsystem' has no member named 'entry'. |
| 2 | Field nr_events has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct event_subsystem' has no member named 'nr_events'. |
| Change | Effect | |
|---|---|---|
| 1 | Field buffer has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_array' has no member named 'buffer'. |
| 2 | Field data has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_array' has no member named 'data'. |
| 3 | Field time_start has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct trace_array' has no member named 'time_start'. |
| 4 | Field cpu has been renamed to name. | Recompilation of a client program may be broken with the error message: struct trace_array has no member named cpu. |
| Change | Effect | |
|---|---|---|
| 1 | Field allocated_snapshot has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tracer' has no member named 'allocated_snapshot'. |
| 2 | Field use_max_tr has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tracer' has no member named 'use_max_tr'. |
| Change | Effect | |
|---|---|---|
| 1 | Field warned has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct tty_struct' has no member named 'warned'. |
| Change | Effect | |
|---|---|---|
| 1 | Field worker_ida has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct worker_pool' has no member named 'worker_ida'. |
| 2 | Field assoc_mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct worker_pool' has no member named 'assoc_mutex'. |
| Change | Effect | |
|---|---|---|
| 1 | Field flush_mutex has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct workqueue_struct' has no member named 'flush_mutex'. |
| 2 | Field mayday_mask has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct workqueue_struct' has no member named 'mayday_mask'. |
| 3 | Field pool_wq has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct workqueue_struct' has no member named 'pool_wq'. |
| Change | Effect | |
|---|---|---|
| 1 | Field rebind_work has been removed from this type. | Recompilation of a client program may be broken with the error message: 'struct worker' has no member named 'rebind_work'. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter uid of type kuid_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter policy of type struct cpufreq_policy* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd middle parameter minor_id has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter phys_addr of type u64 has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter handle of type handle_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter endtime of type time_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter qop 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 handle of type handle_t* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter start of type unsigned long has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter req of type struct cfg80211_assoc_request* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 5th middle parameter prev_bssid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter req of type struct cfg80211_assoc_request* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| 2 | 5th middle parameter prev_bssid has been removed from the calling stack. | 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 local of type struct ieee80211_local* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter opos of type loff_t* 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 hvpp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 4th middle parameter rvp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter tr of type struct trace_array* has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter queues of type unsigned long has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter queues of type unsigned long has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter action of type bool has been added to the calling stack at the middle position. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field ki_users has been changed from int to struct atomic_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field dead has been changed from int to struct atomic_t of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field info_ent became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct drm_info_node::info_ent'. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field gm_oid has been changed from struct xdr_netobj to struct rpcsec_gss_oid of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field backlight has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field presp has been changed from struct sk_buff to struct beacon_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of field timeout_int has been changed from unsigned char to struct ieee80211_timeout_interval_ie of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The pointer level of field rate_idx_mcs_mask has been increased from 0 to 1. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field dev_lock has been changed from struct mutex to struct semaphore of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field tx_bytes has been changed from unsigned long to u64[4] of different format. | Recompilation of a client program may be broken. |
| 2 | Type of field tx_packets has been changed from unsigned long to u64[4] of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field type became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ftrace_event_field::type'. |
| 2 | Field name became const. | Recompilation of a client program may be broken with the error message: assignment of read-only member/location 'struct ftrace_event_field::name'. |
| 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 | Parameter type of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 6th parameter loginuid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 7th parameter sessionid has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 8th parameter sid 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 | Type of 1st parameter cgrp has been changed from struct cgroup const* to struct cgroup* (became non-const). | Recompilation of a client program may be broken. |
| 2 | Base type of parameter task has been changed from struct task_struct to struct cgroup of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter gid of type kgid_t* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dbs_data has been changed from struct dbs_data to struct cpufreq_policy of different format. | Recompilation of a client program may be broken. |
| 2 | Base type of parameter policy has been changed from struct cpufreq_policy to struct common_dbs_data of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter io_busy of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter init of type void(*)(void*) has been added to the calling stack. | Recompilation of a client program may be broken. |
| 2 | Parameter release of type void(*)(void*) has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter data_len of type u32 has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter obj has been changed from struct xdr_netobj to struct rpcsec_gss_oid of different format. | 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 | Parameter plane of type int has been added to the calling stack. | 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_key of different format. | Recompilation of a client program may be broken. |
| 2 | The pointer level of 2nd parameter key has been increased from 1 to 0. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dying has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter end of type unsigned long has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 10th parameter use_mfp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 11th parameter crypt has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 12th parameter assoc_flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 4 | 13th parameter ht_capa has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 5 | 14th parameter ht_capa_mask has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 6 | 8th parameter ie has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 7 | 9th parameter ie_len has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 10th parameter use_mfp has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 2 | 11th parameter crypt has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 3 | 12th parameter assoc_flags has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 4 | 13th parameter ht_capa has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 5 | 14th parameter ht_capa_mask has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 6 | 8th parameter ie has been removed from the calling stack. | Recompilation of a client program may be broken. |
| 7 | 9th parameter ie_len has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dentry has been changed from struct dentry to struct mountpoint of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter kill has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter stateid of type nfs4_stateid const* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter inode has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter inode has been changed from struct inode to struct pipe_inode_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter dest_dentry has been changed from struct dentry to struct mountpoint of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dev 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 | 1st parameter dev has been removed from the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter root_irq_dir 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 | Parameter list of type struct list_head* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter offs_tai of type ktime_t* has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter skip of type int has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tr has been changed from struct trace_array to struct trace_buffer of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter tr has been changed from struct trace_array to struct trace_buffer of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of parameter system has been changed from struct event_subsystem to struct ftrace_subsystem_dir of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of return value has been changed from char to struct acpi_exception_info of different format. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Parameter func of type void(*)(struct callback_head*) has been added to the calling stack. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field argument_list has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field return_btype has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hotplug 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 ki_cancel has been changed from int(*)(struct kiocb*, struct io_event*) to int()(struct kiocb*, struct io_event*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field internal_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field mmap_base has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field nr_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field nr_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field rcu_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field ring_pages has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field info2flavor has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field flavor2info has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dwork has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rescue_workqueue has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field rescue_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rescue_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field rescue_work 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 release has been changed from int(*)(struct gendisk*, fmode_t) to void(*)(struct gendisk*, fmode_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vht_capa_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_capa_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vht_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field crit_proto_start has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field crit_proto_stop has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field update_ft_ies has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_mpm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_capa_mod_mask 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. |
| Change | Effect | |
|---|---|---|
| 1 | Field crit_proto_nlportid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field have_governor_per_policy has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field governor_data has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field kobjs has been changed from struct cpuidle_state_kobj*[8] to struct cpuidle_state_kobj*[10]. | Recompilation of a client program may be broken. |
| 2 | Type of field states_usage has been changed from struct cpuidle_state_usage[8] to struct cpuidle_state_usage[10]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field states has been changed from struct cpuidle_state[8] to struct cpuidle_state[10]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock_key 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 devnode has been changed from char*(*)(struct device*, umode_t*) to char*(*)(struct device*, umode_t*, kuid_t*, kgid_t*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field exp_name has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field list_node has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field initial_config 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. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from int()(struct request_queue*) to int()(struct request_queue*, struct elevator_type*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field s_resv_clusters has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nfs_build_inode_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field skip_vt_switch has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field files has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Type of field flags has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field trace_buffer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field module has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field parallel_ops 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 gss_import_sec_context has been changed from int(*)(void const*, size_t, struct gss_ctx*, gfp_t) to int(*)(void const*, size_t, struct gss_ctx*, time_t*, gfp_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field qop has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field kvm_posted_intr_ipis has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field is_headphone_mic has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field is_headset_mic has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field playing has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_delay has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field add_jack_modes has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field beep_nid has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field extra_out_badness has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field hp_mic has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field hp_mic_jack_modes has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field hp_mic_mux_idx has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field hp_mic_pin has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field main_out_badness has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field suppress_hp_mic_detect has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field byte2 has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field freq has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field channels has been changed from int to u8. | Recompilation of a client program may be broken. |
| 4 | Type of field format has been changed from int to u8. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field debug_list_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field driver_input_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field io_started has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field idle has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field request has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field wait has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field clock_base has been changed from struct hrtimer_clock_base[3] to struct hrtimer_clock_base[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field wakeup_enabled_descendants has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field bus_recovery_info has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field get_pipe_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field crtc_mode_set has been changed from int(*)(struct drm_crtc*, struct drm_display_mode*, struct drm_display_mode*, int, int, struct drm_framebuffer*) to int(*)(struct drm_crtc*, int, int, struct drm_framebuffer*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ctx has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field fence has been changed from u64[16] to u64[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field hotplug_reenable_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field hpd_stats has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field num_plane has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Type of field fence_regs has been changed from struct drm_i915_fence_reg[16] to struct drm_i915_fence_reg[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field enable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field saveFENCE has been changed from uint64_t[16] to uint64_t[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_pipes has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field hw_max has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cur has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field variable has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field vht_capa has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vht_capa_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field p2p_noa_index has been changed from u8 to s16. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field user_mpm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field _oper_chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field csa_chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field type has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field crypto_tx_tailroom_pending_dec has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dec_tailroom_needed_wk has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field rc_has_mcs_mask has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field rate has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field ext_chansw_ie has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field sec_chan_offs has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field wide_bw_chansw_ie has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field token has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field tokenized has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field hash has been changed from struct hlist_head[64] to struct inet_frag_bucket[1024]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field polled has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field config has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field aux_ch_ctl_reg has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field compute_config has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field hpd_pin has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field mode_set has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dest_trash_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field dest_trash_timer has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field rs_table has been changed from struct list_head[16] to struct hlist_head[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field ecn has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field dev_addr_genid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field short_preamble has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field skip_table has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field use_cts_prot has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field use_rts has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field p2p_noa_attr has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field chandef has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field uapsd_max_sp_len has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field uapsd_queues has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_multicast_list has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Base type of field flush has been changed from void(*)(struct ieee80211_hw*, bool) to void(*)(struct ieee80211_hw*, u32, bool). | Recompilation of a client program may be broken. |
| 3 | Base type of field remain_on_channel has been changed from int(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct ieee80211_channel*, int) to int(*)(struct ieee80211_hw*, struct ieee80211_vif*, struct ieee80211_channel*, int, enum ieee80211_roc_type). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field rates has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field acm has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field rate_idx_mcs_mask has been changed from u8[10] to u8*. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field mmap_legacy_base has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mnt_mp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field spin_mlock has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nf 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 ndo_vlan_rx_add_vid has been changed from int(*)(struct net_device*, unsigned short) to int(*)(struct net_device*, __be16, u16). | Recompilation of a client program may be broken. |
| 2 | Base type of field ndo_vlan_rx_kill_vid has been changed from int(*)(struct net_device*, unsigned short) to int(*)(struct net_device*, __be16, u16). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type has been changed from void()(u_int8_t, unsigned int, struct sk_buff const*, struct net_device const*, struct net_device const*, struct nf_loginfo const*, char const*) to void()(struct net*, u_int8_t, unsigned int, struct sk_buff const*, struct net_device const*, struct net_device const*, struct nf_loginfo const*, char const*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field size has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field free_lock_state has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field init_caps has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field slot_tbl_state has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field io_count has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field flavors has been changed from struct nfs4_secinfo_flavor[] to struct nfs4_secinfo4[]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field stateid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field stateid has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field msi_cap has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field msix_cap has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Type of field pm_cap has been changed from int to u8. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field regs has been changed from struct er_account[3] to struct er_account[4]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field data_src has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field weight has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field cpu_events has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field event_attrs has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_wol has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field get_wol has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field set_vbus has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field proc_self has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field files has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field t_hash has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field num_supplies has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field supplied_from has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field x86_capability has been changed from __u32[10] to __u32[11]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field need_future_gp has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field abbr has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field wakeup_work 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 rtx_syn_ack has been changed from int(*)(struct sock*, struct request_sock*, struct request_values*) to int(*)(struct sock*, struct request_sock*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_work has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field irq_work 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 int(*)(struct sk_buff*, struct nlmsghdr*, void*) to int(*)(struct sk_buff*, struct nlmsghdr*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field linklayer has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field nohz_idle has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field audit_tty_log_passwd has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field posix_timer_id has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field write_info 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 sb_clone_mnt_opts has been changed from void(*)(struct super_block const*, struct super_block*) to int(*)(struct super_block const*, struct super_block*). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pending_alter has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field pending_const has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field sem_otime has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field pending_alter has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field inner_mac_header has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field vlan_proto has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[27] to unsigned long[28]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[5] to unsigned long[6]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from atomic_long_t[5] to atomic_long_t[6]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from u64[31] to u64[32]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[92] to unsigned long[95]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[15] to unsigned long[16]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of field mibs has been changed from unsigned long[7] to unsigned long[8]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field sk_pacing_rate has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field opos 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_bytes has been changed from unsigned long to u64. | Recompilation of a client program may be broken. |
| 2 | Type of field tx_fragments has been changed from unsigned long to u32. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field frto has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field tlp_high_seq has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field clock_id has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field current_trace has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field dir has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field event_dir has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field events has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field list has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field options has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Field percpu_dir has been added to this type. | This field will not be initialized or used by old client applications. |
| 10 | Field ref has been added to this type. | This field will not be initialized or used by old client applications. |
| 11 | Field start_lock has been added to this type. | This field will not be initialized or used by old client applications. |
| 12 | Field stop_count has been added to this type. | This field will not be initialized or used by old client applications. |
| 13 | Field systems has been added to this type. | This field will not be initialized or used by old client applications. |
| 14 | Field trace_buffer has been added to this type. | This field will not be initialized or used by old client applications. |
| 15 | Field trace_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field trace_cpu has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flow_change has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field level has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field mayday_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field pwqs_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field refcnt has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field unbound_release_work has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field rcu 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. |
| 2 | Field rcu has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field node has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field hash_node has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field refcnt has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field manager_mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field manager_arb has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field worker_idr has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Type of field cpu has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field dfl_pwq has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field cpu_pwqs has been added to this type. | This field will not be initialized or used by old client applications. |
| 3 | Field unbound_attrs has been added to this type. | This field will not be initialized or used by old client applications. |
| 4 | Field numa_pwq_tbl has been added to this type. | This field will not be initialized or used by old client applications. |
| 5 | Field maydays has been added to this type. | This field will not be initialized or used by old client applications. |
| 6 | Field mutex has been added to this type. | This field will not be initialized or used by old client applications. |
| 7 | Field pwqs has been added to this type. | This field will not be initialized or used by old client applications. |
| 8 | Field wq_dev has been added to this type. | This field will not be initialized or used by old client applications. |
| 9 | Type of field name has been changed from char[] to char[24]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Field desc_valid has been added to this type. | This field will not be initialized or used by old client applications. |
| 2 | Field desc has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field extra_flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Field flags has been added to this type. | This field will not be initialized or used by old client applications. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct pci_device_id[5] const to struct pci_device_id[7] const. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter ptr has been changed from void()(void*, async_cookie_t) to void(*)(void*, async_cookie_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Base type of 1st parameter ptr has been changed from void()(void*, async_cookie_t) to void(*)(void*, async_cookie_t). | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from u32 to rpc_authflavor_t. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter key has been changed from struct ieee80211_key* to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct event_constraint[11] to struct event_constraint[12]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from struct event_constraint[11] to struct event_constraint[12]. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of this global data has been changed from int to bool. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter device has been changed from struct acpi_device* to acpi_handle. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter cpu has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 1st parameter cpu has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter cpu has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | Type of 2nd parameter cpu has been changed from unsigned int to int. | Recompilation of a client program may be broken. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field max_reqs has been changed from 5 to 4. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field dev has been changed from 3 to 5. | No effect. |
| 2 | The relative position of field mode has been changed from 4 to 6. | No effect. |
| 3 | The relative position of field uid has been changed from 5 to 7. | No effect. |
| 4 | The relative position of field fcap has been changed from 9 to 11. | No effect. |
| 5 | The relative position of field fcap_ver has been changed from 10 to 12. | No effect. |
| 6 | The relative position of field gid has been changed from 6 to 8. | No effect. |
| 7 | The relative position of field name_len has been changed from 11 to 2. | No effect. |
| 8 | The relative position of field ino has been changed from 2 to 4. | No effect. |
| 9 | The relative position of field rdev has been changed from 7 to 9. | No effect. |
| 10 | The relative position of field name_put has been changed from 13 to 3. | No effect. |
| 11 | The relative position of field osid has been changed from 8 to 10. | No effect. |
| 12 | The relative position of field type has been changed from 12 to 13. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field allow_utime has been changed from 10 to 11. | No effect. |
| 2 | The relative position of field discard has been changed from 24 to 25. | No effect. |
| 3 | The relative position of field dotsOK has been changed from 14 to 15. | No effect. |
| 4 | The relative position of field flush has been changed from 19 to 20. | No effect. |
| 5 | The relative position of field isvfat has been changed from 15 to 16. | No effect. |
| 6 | The relative position of field nfs has been changed from 25 to 10. | No effect. |
| 7 | The relative position of field nocase has been changed from 20 to 21. | No effect. |
| 8 | The relative position of field numtail has been changed from 18 to 19. | No effect. |
| 9 | The relative position of field quiet has been changed from 11 to 12. | No effect. |
| 10 | The relative position of field rodir has been changed from 23 to 24. | No effect. |
| 11 | The relative position of field showexec has been changed from 12 to 13. | No effect. |
| 12 | The relative position of field sys_immutable has been changed from 13 to 14. | No effect. |
| 13 | The relative position of field tz_set has been changed from 22 to 23. | No effect. |
| 14 | The relative position of field unicode_xlate has been changed from 17 to 18. | No effect. |
| 15 | The relative position of field usefree has been changed from 21 to 22. | No effect. |
| 16 | The relative position of field utf8 has been changed from 16 to 17. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member FIX_RO_IDT with value 70 has been added. | No effect. |
| 2 | Value of member FIX_BTMAP_END has been changed from 233 to 234. | No effect. |
| 3 | Value of member FIX_KMAP_END has been changed from 229 to 230. | No effect. |
| 4 | Value of member FIX_BTMAP_BEGIN has been changed from 488 to 489. | No effect. |
| 5 | Value of member FIX_KMAP_BEGIN has been changed from 70 to 71. | No effect. |
| 6 | Value of member FIX_PCIE_MCFG has been changed from 230 to 231. | No effect. |
| 7 | Value of member FIX_TEXT_POKE0 has been changed from 232 to 233. | No effect. |
| 8 | Value of member FIX_TEXT_POKE1 has been changed from 231 to 232. | No effect. |
| 9 | Value of member FIX_WP_TEST has been changed from 489 to 490. | No effect. |
| 10 | Value of member __end_of_fixed_addresses has been changed from 490 to 491. | No effect. |
| 11 | Value of member __end_of_permanent_fixed_addresses has been changed from 233 to 234. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field cpu has been changed from 13 to 15. | No effect. |
| 2 | The relative position of field ent has been changed from 9 to 11. | No effect. |
| 3 | The relative position of field ent_size has been changed from 12 to 14. | No effect. |
| 4 | The relative position of field idx has been changed from 16 to 18. | No effect. |
| 5 | The relative position of field leftover has been changed from 11 to 13. | No effect. |
| 6 | The relative position of field lost_events has been changed from 10 to 12. | No effect. |
| 7 | The relative position of field pos has been changed from 15 to 17. | No effect. |
| 8 | The relative position of field seq has been changed from 8 to 10. | No effect. |
| 9 | The relative position of field snapshot has been changed from 18 to 9. | No effect. |
| 10 | The relative position of field started has been changed from 17 to 8. | No effect. |
| 11 | The relative position of field ts has been changed from 14 to 16. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field channels has been changed from 0 to 1. | No effect. |
| 2 | The relative position of field format has been changed from 1 to 0. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member PCH_NOP with value 4 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field backlight has been changed from 90 to 36. | No effect. |
| 2 | The relative position of field bios_lvds_val has been changed from 46 to 47. | No effect. |
| 3 | The relative position of field child_dev has been changed from 79 to 80. | No effect. |
| 4 | The relative position of field child_dev_num has been changed from 78 to 79. | No effect. |
| 5 | The relative position of field compressed_fb has been changed from 85 to 86. | No effect. |
| 6 | The relative position of field compressed_llb has been changed from 86 to 87. | No effect. |
| 7 | The relative position of field console_resume_work has been changed from 89 to 90. | No effect. |
| 8 | The relative position of field crt_ddc_pin has been changed from 49 to 50. | No effect. |
| 9 | The relative position of field ddi_plls has been changed from 73 to 74. | No effect. |
| 10 | The relative position of field display has been changed from 57 to 58. | No effect. |
| 11 | The relative position of field display_clock_mode has been changed from 43 to 44. | No effect. |
| 12 | The relative position of field edp has been changed from 47 to 48. | No effect. |
| 13 | The relative position of field fbdev has been changed from 88 to 89. | No effect. |
| 14 | The relative position of field fdi_rx_polarity_inverted has been changed from 44 to 45. | No effect. |
| 15 | The relative position of field fence_reg_start has been changed from 51 to 52. | No effect. |
| 16 | The relative position of field fence_regs has been changed from 50 to 51. | No effect. |
| 17 | The relative position of field fsb_freq has been changed from 53 to 54. | No effect. |
| 18 | The relative position of field gpu_error has been changed from 87 to 88. | No effect. |
| 19 | The relative position of field gtt has been changed from 63 to 64. | No effect. |
| 20 | The relative position of field int_crt_support has been changed from 41 to 42. | No effect. |
| 21 | The relative position of field int_tv_support has been changed from 38 to 39. | No effect. |
| 22 | The relative position of field ips has been changed from 83 to 84. | No effect. |
| 23 | The relative position of field is_ddr3 has been changed from 55 to 56. | No effect. |
| 24 | The relative position of field l3_parity has been changed from 81 to 82. | No effect. |
| 25 | The relative position of field lfp_lvds_vbt_mode has been changed from 36 to 37. | No effect. |
| 26 | The relative position of field lvds_border_bits has been changed from 66 to 67. | No effect. |
| 27 | The relative position of field lvds_dither has been changed from 39 to 40. | No effect. |
| 28 | The relative position of field lvds_downclock has been changed from 76 to 77. | No effect. |
| 29 | The relative position of field lvds_downclock_avail has been changed from 75 to 76. | No effect. |
| 30 | The relative position of field lvds_ssc_freq has been changed from 45 to 46. | No effect. |
| 31 | The relative position of field lvds_use_ssc has been changed from 42 to 43. | No effect. |
| 32 | The relative position of field lvds_vbt has been changed from 40 to 41. | No effect. |
| 33 | The relative position of field mchbar_need_disable has been changed from 80 to 81. | No effect. |
| 34 | The relative position of field mem_freq has been changed from 54 to 55. | No effect. |
| 35 | The relative position of field mm has been changed from 64 to 65. | No effect. |
| 36 | The relative position of field modeset_restore has been changed from 61 to 62. | No effect. |
| 37 | The relative position of field modeset_restore_lock has been changed from 62 to 63. | No effect. |
| 38 | The relative position of field no_aux_handshake has been changed from 48 to 49. | No effect. |
| 39 | The relative position of field no_fbc_reason has been changed from 84 to 85. | No effect. |
| 40 | The relative position of field num_fence_regs has been changed from 52 to 53. | No effect. |
| 41 | The relative position of field orig_clock has been changed from 77 to 78. | No effect. |
| 42 | The relative position of field pch_id has been changed from 59 to 60. | No effect. |
| 43 | The relative position of field pch_pf_pos has been changed from 67 to 68. | No effect. |
| 44 | The relative position of field pch_pf_size has been changed from 68 to 69. | No effect. |
| 45 | The relative position of field pch_plls has been changed from 72 to 73. | No effect. |
| 46 | The relative position of field pch_type has been changed from 58 to 59. | No effect. |
| 47 | The relative position of field pending_flip_queue has been changed from 71 to 72. | No effect. |
| 48 | The relative position of field pipe_to_crtc_mapping has been changed from 70 to 71. | No effect. |
| 49 | The relative position of field plane_to_crtc_mapping has been changed from 69 to 70. | No effect. |
| 50 | The relative position of field quirks has been changed from 60 to 61. | No effect. |
| 51 | The relative position of field render_reclock_avail has been changed from 74 to 75. | No effect. |
| 52 | The relative position of field rps has been changed from 82 to 83. | No effect. |
| 53 | The relative position of field sdvo_lvds_vbt_mode has been changed from 37 to 38. | No effect. |
| 54 | The relative position of field sdvo_mappings has been changed from 65 to 66. | No effect. |
| 55 | The relative position of field wq has been changed from 56 to 57. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Field ext_chan_switch has been added to this type. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member IEEE80211_QUEUE_STOP_REASON_FLUSH with value 7 has been added. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field addr_list_lock has been changed from 41 to 42. | No effect. |
| 2 | The relative position of field hw_enc_features has been changed from 15 to 16. | No effect. |
| 3 | The relative position of field hard_header_len has been changed from 33 to 34. | No effect. |
| 4 | The relative position of field allmulti has been changed from 46 to 49. | No effect. |
| 5 | The relative position of field ip_ptr has been changed from 48 to 51. | No effect. |
| 6 | The relative position of field real_num_rx_queues has been changed from 61 to 60. | No effect. |
| 7 | The relative position of field mtu has been changed from 31 to 32. | No effect. |
| 8 | The relative position of field upper_dev_list has been changed from 54 to 11. | No effect. |
| 9 | The relative position of field broadcast has been changed from 57 to 64. | No effect. |
| 10 | The relative position of field link_mode has been changed from 28 to 29. | No effect. |
| 11 | The relative position of field _rx has been changed from 59 to 58. | No effect. |
| 12 | The relative position of field netdev_ops has been changed from 20 to 21. | No effect. |
| 13 | The relative position of field header_ops has been changed from 22 to 23. | No effect. |
| 14 | The relative position of field uc has been changed from 42 to 43. | No effect. |
| 15 | The relative position of field flags has been changed from 23 to 24. | No effect. |
| 16 | The relative position of field needed_headroom has been changed from 34 to 35. | No effect. |
| 17 | The relative position of field dn_ptr has been changed from 49 to 52. | No effect. |
| 18 | The relative position of field dev_addr has been changed from 55 to 57. | No effect. |
| 19 | The relative position of field addr_assign_type has been changed from 37 to 38. | No effect. |
| 20 | The relative position of field operstate has been changed from 27 to 28. | No effect. |
| 21 | The relative position of field rx_handler_data has been changed from 64 to 62. | No effect. |
| 22 | The relative position of field tx_queue_len has been changed from 70 to 69. | No effect. |
| 23 | The relative position of field dev_id has been changed from 40 to 41. | No effect. |
| 24 | The relative position of field queues_kset has been changed from 58 to 46. | No effect. |
| 25 | The relative position of field last_rx has been changed from 53 to 56. | No effect. |
| 26 | The relative position of field xps_maps has been changed from 72 to 71. | No effect. |
| 27 | The relative position of field ax25_ptr has been changed from 51 to 54. | No effect. |
| 28 | The relative position of field type has been changed from 32 to 33. | No effect. |
| 29 | The relative position of field rx_handler has been changed from 63 to 61. | No effect. |
| 30 | The relative position of field promiscuity has been changed from 45 to 48. | No effect. |
| 31 | The relative position of field rx_cpu_rmap has been changed from 62 to 72. | No effect. |
| 32 | The relative position of field rx_dropped has been changed from 19 to 20. | No effect. |
| 33 | The relative position of field ifindex has been changed from 16 to 17. | No effect. |
| 34 | The relative position of field gflags has been changed from 25 to 26. | No effect. |
| 35 | The relative position of field perm_addr has been changed from 36 to 37. | No effect. |
| 36 | The relative position of field stats has been changed from 18 to 19. | No effect. |
| 37 | The relative position of field features has been changed from 11 to 12. | No effect. |
| 38 | The relative position of field qdisc has been changed from 69 to 68. | No effect. |
| 39 | The relative position of field iflink has been changed from 17 to 18. | No effect. |
| 40 | The relative position of field addr_len has been changed from 38 to 39. | No effect. |
| 41 | The relative position of field dma has been changed from 30 to 31. | No effect. |
| 42 | The relative position of field atalk_ptr has been changed from 47 to 50. | No effect. |
| 43 | The relative position of field tx_global_lock has been changed from 71 to 70. | No effect. |
| 44 | The relative position of field if_port has been changed from 29 to 30. | No effect. |
| 45 | The relative position of field wanted_features has been changed from 13 to 14. | No effect. |
| 46 | The relative position of field needed_tailroom has been changed from 35 to 36. | No effect. |
| 47 | The relative position of field dev_addrs has been changed from 56 to 45. | No effect. |
| 48 | The relative position of field hw_features has been changed from 12 to 13. | No effect. |
| 49 | The relative position of field num_rx_queues has been changed from 60 to 59. | No effect. |
| 50 | The relative position of field vlan_features has been changed from 14 to 15. | No effect. |
| 51 | The relative position of field _tx has been changed from 66 to 65. | No effect. |
| 52 | The relative position of field padded has been changed from 26 to 27. | No effect. |
| 53 | The relative position of field ieee80211_ptr has been changed from 52 to 55. | No effect. |
| 54 | The relative position of field ingress_queue has been changed from 65 to 63. | No effect. |
| 55 | The relative position of field num_tx_queues has been changed from 67 to 66. | No effect. |
| 56 | The relative position of field real_num_tx_queues has been changed from 68 to 67. | No effect. |
| 57 | The relative position of field uc_promisc has been changed from 44 to 47. | No effect. |
| 58 | The relative position of field ethtool_ops has been changed from 21 to 22. | No effect. |
| 59 | The relative position of field mc has been changed from 43 to 44. | No effect. |
| 60 | The relative position of field ip6_ptr has been changed from 50 to 53. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Reserved field __reserved has been replaced by linklayer. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field count has been changed from 13 to 12. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The member RFKILL_TYPE_NFC with value 8 has been added. | No effect. |
| 2 | Value of member NUM_RFKILL_TYPES has been changed from 8 to 9. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field tx_bytes has been changed from 36 to 37. | No effect. |
| 2 | The relative position of field tx_fragments has been changed from 37 to 35. | No effect. |
| 3 | The relative position of field tx_packets has been changed from 35 to 36. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field nonagle has been changed from 23 to 24. | No effect. |
| 2 | The relative position of field repair has been changed from 26 to 27. | No effect. |
| 3 | The relative position of field thin_dupack has been changed from 25 to 26. | No effect. |
| 4 | The relative position of field thin_lto has been changed from 24 to 25. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | The relative position of field saved_max_active has been changed from 10 to 9. | No effect. |
| 2 | The relative position of field work_color has been changed from 2 to 1. | No effect. |
| 3 | The relative position of field list has been changed from 1 to 0. | No effect. |
| 4 | The relative position of field first_flusher has been changed from 5 to 4. | No effect. |
| 5 | The relative position of field nr_drainers has been changed from 9 to 8. | No effect. |
| 6 | The relative position of field flusher_overflow has been changed from 7 to 6. | No effect. |
| 7 | The relative position of field flush_color has been changed from 3 to 2. | No effect. |
| 8 | The relative position of field nr_pwqs_to_flush has been changed from 4 to 3. | No effect. |
| 9 | The relative position of field rescuer has been changed from 8 to 7. | No effect. |
| 10 | The relative position of field flusher_queue has been changed from 6 to 5. | No effect. |
| 11 | The relative position of field name has been changed from 11 to 10. | No effect. |
| 12 | The relative position of field flags has been changed from 0 to 11. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ptr has been renamed to func. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter ptr has been renamed to func. | 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 | 2nd parameter task has been renamed to ancestor. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter dbs_data has been renamed to policy. | No effect. |
| 2 | 2nd parameter policy has been renamed to cdata. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter next_state has been renamed to index. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter sdvox_reg has been renamed to hdmi_reg. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter local has been renamed to key. | No effect. |
| 2 | 2nd parameter key has been renamed to delay_tailroom. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 4th parameter current_nid has been renamed to page_nid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter macaddr has been renamed to addr. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter dentry has been renamed to mp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter pid has been renamed to portid. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 3rd parameter pid has been renamed to portid. | 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 inode has been renamed to pipe. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter dest_dentry has been renamed to dest_mp. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 2nd parameter data has been renamed to csd. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tr has been renamed to buf. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter tr has been renamed to buf. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to int. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter system has been renamed to dir. | 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 acpi_status. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | 1st parameter device has been renamed to handle. | No effect. |
| Change | Effect | |
|---|---|---|
| 1 | Type of return value has been changed from void to struct vc_data*. | No effect. |