public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29300] New: btrfs-progs fails self-compare only on ppc64le
Date: Wed, 29 Jun 2022 19:22:50 +0000	[thread overview]
Message-ID: <bug-29300-9487@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29300
           Summary: btrfs-progs fails self-compare only on ppc64le
           Product: libabigail
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
          Assignee: dodji at redhat dot com
          Reporter: woodard at redhat dot com
                CC: libabigail at sourceware dot org
  Target Milestone: ---

This only happens on ppc64le, the check passes on x86_64.

Comparing the ABI of binaries between btrfs-progs-5.18-1.fc36.ppc64le.rpm and
btrfs-progs-5.18-1.fc36.ppc64le.rpm:

======== comparing'btrfs' to itself wrongly yielded result: ===========
  Functions changes summary: 0 Removed, 0 Changed (53 filtered out), 0 Added
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

===SELF CHECK FAILED for 'btrfs'
==== SELF CHECK SUCCEEDED for 'btrfs-convert' ====
==== SELF CHECK SUCCEEDED for 'mkfs.btrfs' ====
======== comparing'btrfs-image' to itself wrongly yielded result: ===========
  Functions changes summary: 0 Removed, 0 Changed (53 filtered out), 0 Added
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

===SELF CHECK FAILED for 'btrfs-image'
==== SELF CHECK SUCCEEDED for 'btrfs-find-root' ====
======== comparing'btrfstune' to itself wrongly yielded result: ===========
  Functions changes summary: 0 Removed, 0 Changed (53 filtered out), 0 Added
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

===SELF CHECK FAILED for 'btrfstune'
======== comparing'btrfs-map-logical' to itself wrongly yielded result:
===========
  Functions changes summary: 0 Removed, 0 Changed (53 filtered out), 0 Added
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

===SELF CHECK FAILED for 'btrfs-map-logical'
======== comparing'btrfs-select-super' to itself wrongly yielded result:
===========
  Functions changes summary: 0 Removed, 0 Changed (53 filtered out), 0 Added
functions
  Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

This is what I did to reproduce it:
$ wget
https://kojipkgs.fedoraproject.org//packages/btrfs-progs/5.18/1.fc36/ppc64le/btrfs-progs-5.18-1.fc36.ppc64le.rpm
$ rpm2cpio btrfs-progs-5.18-1.fc36.ppc64le.rpm | cpio -icumdv
$ abidw --abidiff usr/sbin/btrfs

The crux of the issue is, everything else is a duplicate of this change:

Functions changes summary: 0 Removed, 53 Changed, 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

53 functions with some indirect sub-type change:

  [C] 'function int __btrfs_map_block(btrfs_fs_info*, int, u64, u64*, u64*,
btrfs_multi_bio**, int, u64**)' at volumes.c:1798:1 has some indirect sub-type
changes:
    parameter 1 of type 'btrfs_fs_info*' has sub-type changes:
      in pointed to type 'struct btrfs_fs_info' at ctree.h:1199:1:
        type size hasn't changed
        1 data member change:
          type of 'btrfs_trans_handle* running_transaction' changed:
            in pointed to type 'struct btrfs_trans_handle' at
transaction.h:27:1:
              type size hasn't changed
              1 data member change:
                type of 'btrfs_fs_info* fs_info' changed:
                  pointed to type 'struct btrfs_fs_info' changed, as being
reported
    parameter 6 of type 'btrfs_multi_bio**' has sub-type changes:
      in pointed to type 'btrfs_multi_bio*':
        in pointed to type 'struct btrfs_multi_bio' at volumes.h:107:1:
          type size hasn't changed
          1 data member change:
            type of 'btrfs_bio_stripe stripes[]' changed:
              array element type 'struct btrfs_bio_stripe' changed:
                type size hasn't changed
                1 data member change:
                  type of 'btrfs_device* dev' changed:
                    in pointed to type 'struct btrfs_device' at volumes.h:28:1:
                      type size hasn't changed
                      1 data member change:
                        type of 'btrfs_fs_info* fs_info' changed:
                          pointed to type 'struct btrfs_fs_info' changed at
ctree.h:1199:1, as reported earlier
              type size hasn't changed

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

             reply	other threads:[~2022-06-29 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 19:22 woodard at redhat dot com [this message]
2022-06-29 19:23 ` [Bug default/29300] " woodard at redhat dot com
2022-06-29 21:05 ` woodard at redhat dot com
2022-06-29 21:12 ` woodard at redhat dot com
2022-07-04 12:55 ` dodji at redhat dot com
2022-07-26 19:47 ` woodard at redhat 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-29300-9487@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).