public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Pavlu <petr.pavlu@suse.com>
To: Sami Tolvanen <samitolvanen@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Matthew Maurer <mmaurer@google.com>,
	Alex Gaynor <alex.gaynor@gmail.com>, Gary Guo <gary@garyguo.net>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Daniel Gomez <da.gomez@samsung.com>, Neal Gompa <neal@gompa.dev>,
	Hector Martin <marcan@marcan.st>, Janne Grunau <j@jannau.net>,
	Miroslav Benes <mbenes@suse.cz>,
	Asahi Linux <asahi@lists.linux.dev>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-modules@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v6 09/18] gendwarfksyms: Limit structure expansion
Date: Mon, 2 Dec 2024 17:14:24 +0100	[thread overview]
Message-ID: <409987f4-d124-48f7-b49c-dd61a4798bef@suse.com> (raw)
In-Reply-To: <20241121204220.2378181-29-samitolvanen@google.com>

On 11/21/24 21:42, Sami Tolvanen wrote:
> Expand each structure type only once per exported symbol. This
> is necessary to support self-referential structures, which would
> otherwise result in infinite recursion, and it's sufficient for
> catching ABI changes.
> 
> Types defined in .c files are opaque to external users and thus
> cannot affect the ABI. Consider type definitions in .c files to
> be declarations to prevent opaque types from changing symbol
> versions.

Thanks for adding support for skipping types defined in .c files. That
is a useful feature that genksyms has.

I was also recently thinking that it would be great if genksyms could
skip definitions that are in internal header files, for example,
kernel/events/internal.h. Perhaps something that could be added in the
future..

I've noted one nit below, but the patch looks sensible to me, feel free
to use:
Reviewed-by: Petr Pavlu <petr.pavlu@suse.com>

> @@ -79,6 +80,55 @@ static bool match_export_symbol(struct state *state, Dwarf_Die *die)
>  	return !!state->sym;
>  }
>  
> +/* DW_AT_decl_file -> struct srcfile */
> +static struct cache srcfile_cache;
> +
> +static bool is_definition_private(Dwarf_Die *die)
> +{
> +	Dwarf_Word filenum;
> +	Dwarf_Files *files;
> +	Dwarf_Die cudie;
> +	const char *s;
> +	int res;
> +
> +	/*
> +	 * Definitions in .c files cannot change the public ABI,
> +	 * so consider them private.
> +	 */
> +	if (!get_udata_attr(die, DW_AT_decl_file, &filenum))
> +		return false;
> +
> +	res = cache_get(&srcfile_cache, filenum);
> +	if (res >= 0)
> +		return !!res;
> +
> +	if (!dwarf_cu_die(die->cu, &cudie, NULL, NULL, NULL, NULL, NULL, NULL))
> +		error("dwarf_cu_die failed: '%s'", dwarf_errmsg(-1));
> +
> +	if (dwarf_getsrcfiles(&cudie, &files, NULL))
> +		error("dwarf_getsrcfiles failed: '%s'", dwarf_errmsg(-1));
> +
> +	s = dwarf_filesrc(files, filenum, NULL, NULL);
> +	if (!s)
> +		error("dwarf_filesrc failed: '%s'", dwarf_errmsg(-1));
> +
> +	s = strrchr(s, '.');
> +	res = s && !strcmp(s, ".c");
> +	cache_set(&srcfile_cache, filenum, res);
> +
> +	return !!res;
> +}
> +
> +static bool is_declaration(Dwarf_Die *die)
> +{
> +	bool value;
> +
> +	if (get_flag_attr(die, DW_AT_declaration, &value) && value)
> +		return true;
> +
> +	return is_definition_private(die);
> +}

Nit: When I read the is_declaration() function in isolation, it is not
clear to me what determining if a definition is private has to do with
the type being a declaration. I think this and related logic in
__process_structure_type() would be easier to follow if the return value
of is_declaration() was negated and the function renamed, for example,
to is_kabi_definition().

-- 
Thanks,
Petr

  reply	other threads:[~2024-12-02 16:14 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 20:42 [PATCH v6 00/18] Implement DWARF modversions Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 01/18] tools: Add gendwarfksyms Sami Tolvanen
2024-11-25 23:29   ` Luis Chamberlain
2024-11-26  3:50     ` Masahiro Yamada
2024-11-26 18:26       ` Luis Chamberlain
2024-12-05  3:46         ` Masahiro Yamada
2024-12-05 15:51           ` Sami Tolvanen
2024-11-26 13:35   ` Masahiro Yamada
2024-12-04 14:13   ` Daniel Gomez
2024-12-05  3:28     ` Masahiro Yamada
2024-11-21 20:42 ` [PATCH v6 02/18] gendwarfksyms: Add address matching Sami Tolvanen
2024-12-02 16:08   ` Petr Pavlu
2024-11-21 20:42 ` [PATCH v6 03/18] gendwarfksyms: Expand base_type Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 04/18] gendwarfksyms: Add a cache for processed DIEs Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 05/18] gendwarfksyms: Expand type modifiers and typedefs Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 06/18] gendwarfksyms: Expand subroutine_type Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 07/18] gendwarfksyms: Expand array_type Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 08/18] gendwarfksyms: Expand structure types Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 09/18] gendwarfksyms: Limit structure expansion Sami Tolvanen
2024-12-02 16:14   ` Petr Pavlu [this message]
2024-11-21 20:42 ` [PATCH v6 10/18] gendwarfksyms: Add die_map debugging Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 11/18] gendwarfksyms: Add symtypes output Sami Tolvanen
2024-12-03 11:54   ` Petr Pavlu
2024-11-21 20:42 ` [PATCH v6 12/18] gendwarfksyms: Add symbol versioning Sami Tolvanen
2024-12-03 11:55   ` Petr Pavlu
2024-11-21 20:42 ` [PATCH v6 13/18] gendwarfksyms: Add support for kABI rules Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 14/18] gendwarfksyms: Add support for reserved and ignored fields Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 15/18] gendwarfksyms: Add support for symbol type pointers Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 16/18] export: Add __gendwarfksyms_ptr_ references to exported symbols Sami Tolvanen
2024-11-21 20:42 ` [PATCH v6 17/18] kbuild: Add gendwarfksyms as an alternative to genksyms Sami Tolvanen
2024-11-26 17:07   ` Masahiro Yamada
2024-11-21 20:42 ` [PATCH v6 18/18] Documentation/kbuild: Add DWARF module versioning Sami Tolvanen
2024-12-14 11:33   ` Masahiro Yamada
2024-12-14 13:04     ` Sedat Dilek
2024-12-17  0:28     ` Sami Tolvanen
2024-11-22  1:51 ` [PATCH v6 00/18] Implement DWARF modversions Sedat Dilek
2024-11-23 11:22   ` Sedat Dilek
2024-11-25  9:34     ` Sami Tolvanen
2024-11-25  9:21   ` Sami Tolvanen
2024-11-25 13:28 ` Neal Gompa
2024-11-25 14:41   ` Miguel Ojeda
2024-11-25 15:34     ` Sami Tolvanen
2024-12-10 12:41       ` Neal Gompa
2024-12-10 14:27         ` Masahiro Yamada
2024-12-11  4:19           ` Luis Chamberlain
2024-11-26 18:30 ` Luis Chamberlain

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=409987f4-d124-48f7-b49c-dd61a4798bef@suse.com \
    --to=petr.pavlu@suse.com \
    --cc=alex.gaynor@gmail.com \
    --cc=asahi@lists.linux.dev \
    --cc=da.gomez@samsung.com \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=j@jannau.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=masahiroy@kernel.org \
    --cc=mbenes@suse.cz \
    --cc=mcgrof@kernel.org \
    --cc=mmaurer@google.com \
    --cc=neal@gompa.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=samitolvanen@google.com \
    --cc=sedat.dilek@gmail.com \
    /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