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/28761] libdovecot-storage.so.0.0.0 fails self-test
Date: Wed, 29 Jun 2022 20:44:06 +0000	[thread overview]
Message-ID: <bug-28761-9487-Nl68Ts2jti@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28761-9487@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Ben Woodard <woodard at redhat dot com> ---
From: zfs-fuse-0.7.2.2-21.fc36.x86_64.rpm and
zfs-fuse-0.7.2.2-21.fc36.x86_64.rpm:

======== comparing'zfs-fuse' to itself wrongly yielded result: ===========
  Functions changes summary: 0 Removed, 0 Changed, 0 Added function
  Variables changes summary: 0 Removed, 0 Changed (6 filtered out), 0 Added
variables

===SELF CHECK FAILED for 'zfs-fuse'

$ abidw /usr/sbin/zfs-fuse > foo
$ abidiff --harmless /usr/sbin/zfs-fuse foo
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 6 Changed, 0 Added variables

6 Changed variables:

  [C] 'vnodeops_t* zfs_dvnodeops' was changed to 'vnodeops* zfs_dvnodeops' at
zfs_znode.c:385:1:
    type of variable changed:
      in pointed to type 'typedef vnodeops_t' at vnode.h:544:1:
        entity changed from 'typedef vnodeops_t' to compatible type 'struct
vnodeops' at vnode.h:544:1

  [C] 'vnodeops_t* zfs_evnodeops' was changed to 'vnodeops* zfs_evnodeops' at
zfs_znode.c:389:1:
    type of variable changed:
      in pointed to type 'typedef vnodeops_t' at vnode.h:544:1:
        entity changed from 'typedef vnodeops_t' to compatible type 'struct
vnodeops' at vnode.h:544:1

  [C] 'vnodeops_t* zfs_fvnodeops' was changed to 'vnodeops* zfs_fvnodeops' at
zfs_znode.c:386:1:
    type of variable changed:
      in pointed to type 'typedef vnodeops_t' at vnode.h:544:1:
        entity changed from 'typedef vnodeops_t' to compatible type 'struct
vnodeops' at vnode.h:544:1

  [C] 'vnodeops_t* zfs_sharevnodeops' was changed to 'vnodeops*
zfs_sharevnodeops' at zfs_znode.c:390:1:
    type of variable changed:
      in pointed to type 'typedef vnodeops_t' at vnode.h:544:1:
        entity changed from 'typedef vnodeops_t' to compatible type 'struct
vnodeops' at vnode.h:544:1

  [C] 'vnodeops_t* zfs_symvnodeops' was changed to 'vnodeops* zfs_symvnodeops'
at zfs_znode.c:387:1:
    type of variable changed:
      in pointed to type 'typedef vnodeops_t' at vnode.h:544:1:
        entity changed from 'typedef vnodeops_t' to compatible type 'struct
vnodeops' at vnode.h:544:1

  [C] 'vnodeops_t* zfs_xdvnodeops' was changed to 'vnodeops* zfs_xdvnodeops' at
zfs_znode.c:388:1:
    type of variable changed:
      in pointed to type 'typedef vnodeops_t' at vnode.h:544:1:
        entity changed from 'typedef vnodeops_t' to compatible type 'struct
vnodeops' at vnode.h:544:1

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

  parent reply	other threads:[~2022-06-29 20:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  2:00 [Bug default/28761] New: " woodard at redhat dot com
2022-01-11  2:00 ` [Bug default/28761] " woodard at redhat dot com
2022-06-29 18:47 ` woodard at redhat dot com
2022-06-29 20:44 ` woodard at redhat dot com [this message]
2022-06-29 20:45 ` woodard at redhat dot com
2022-07-04 12:59 ` dodji at redhat dot com
2022-07-07 15:51 ` 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-28761-9487-Nl68Ts2jti@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).