public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "gprocida+abigail at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/27278] Stray non-diff
Date: Mon, 01 Feb 2021 14:22:00 +0000	[thread overview]
Message-ID: <bug-27278-9487-JYtLoEN61Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27278-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27278

Giuliano Procida <gprocida+abigail at google dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #13175|0                           |1
        is obsolete|                            |

--- Comment #1 from Giuliano Procida <gprocida+abigail at google dot com> ---
Created attachment 13190
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13190&action=edit
two test cases

Here's another case we ran into on the same AOSP branch. We don't often run
without --leaf-changes-only, so this seems to be happening reasonably often.
Reproduced at master.

The archive now also contains c.xml and d.xml. Comparing them with plain
abidiff results in:

Functions changes summary: 0 Removed, 2 Changed (1600 filtered out), 0 Added
functions
Variables changes summary: 0 Removed, 0 Changed (19 filtered out), 0 Added
variables

2 functions with some indirect sub-type change:

  [C] 'function int inet_sk_diag_fill(sock*, inet_connection_sock*, sk_buff*,
const inet_diag_req_v2*, user_namespace*, unsigned int, unsigned int, unsigned
short int, const nlmsghdr*, bool)' at inet_diag.h:39:1 has some indirect
sub-type changes:
    parameter 2 of type 'inet_connection_sock*' has sub-type changes:
      in pointed to type 'struct inet_connection_sock' at
inet_connection_sock.h:89:1:
        type size hasn't changed
        1 data member insertion:
          'u32 inet_connection_sock::icsk_probes_tstamp', at offset 11008 (in
bits) at inet_connection_sock.h:151:1
        1 data member changes (7 filtered):
          type of 'struct {int enabled; int search_high; int search_low; int
probe_size; u32 probe_timestamp;} inet_connection_sock::icsk_mtup' changed:
            type size changed from 160 to 128 (in bits)
            5 data member changes:
              'int enabled' offset changed from 0 to 31 (in bits) (by +31 bits)
              'int search_high' offset changed from 32 to 0 (in bits) (by -32
bits)
              'int search_low' offset changed from 64 to 32 (in bits) (by -32
bits)
              'int probe_size' offset changed from 96 to 64 (in bits) (by -32
bits)
              'u32 probe_timestamp' offset changed from 128 to 96 (in bits) (by
-32 bits)

  [C] 'function unsigned int tcp_slow_start(tcp_sock*, unsigned int)' at
tcp.h:1090:1 has some indirect sub-type changes:
    parameter 1 of type 'tcp_sock*' has sub-type changes:
      in pointed to type 'struct tcp_sock' at tcp.h:138:1:
        type size hasn't changed
        1 data member changes (1 filtered):
          'inet_connection_sock tcp_sock::inet_conn' has *some* difference -
please report as a bug

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-02-01 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 16:45 [Bug default/27278] New: " gprocida+abigail at google dot com
2021-02-01 14:22 ` gprocida+abigail at google dot com [this message]
2021-04-13  9:52 ` [Bug default/27278] " gprocida+abigail at google dot com
2021-05-11 10:13 ` gprocida+abigail at google dot com
2021-07-26 15:57 ` gprocida at google dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27278-9487-JYtLoEN61Z@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).