From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 0F3273858C2D; Thu, 10 Feb 2022 16:46:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0F3273858C2D
From: "gprocida at google dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/26646] unexpected declaration-only types
Date: Thu, 10 Feb 2022 16:46:24 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: libabigail
X-Bugzilla-Component: default
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gprocida at google dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: dodji at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-26646-9487-zAiq5MQ5U2@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26646-9487@http.sourceware.org/bugzilla/>
References: <bug-26646-9487@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: libabigail@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list of the Libabigail project <libabigail.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/libabigail>,
 <mailto:libabigail-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/libabigail/>
List-Help: <mailto:libabigail-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/libabigail>,
 <mailto:libabigail-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2022 16:46:25 -0000

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

--- Comment #16 from gprocida at google dot com ---
I've done a bit more debugging.

Tracing through DIE processing for both vmlinux{3,4} I see that in the form=
er
case, the first and only DIE for struct udp_table that is reached with "cal=
led
from public decl" true is a declaration-only DIE.

So something is preventing the DWARF reader from seeing the (later) definit=
ion
reachable from dev_get_by_name.

Tracing through what happens with dev_get_by_name, I see that recursion sto=
ps
at struct net * which has already been loaded.

In turn that was loaded by function netif_set_real_num_tx_queues -> struct
net_device * -> struct net_device -> struct in_device * -> struct in_device=
 ->
struct net *. This continues struct net -> struct sock * -> struct sock ->
struct proto * -> struct proto. Recursion seems to stop at struct proto, but
I'm not sure why, yet.

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