From: Masahiro Yamada <masahiroy@kernel.org>
To: Sami Tolvanen <samitolvanen@google.com>
Cc: 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 v5 01/19] scripts: move genksyms crc32 implementation to a common include
Date: Sat, 16 Nov 2024 18:08:23 +0900 [thread overview]
Message-ID: <CAK7LNARVK1ZpGXZVTAynuo7CDjgB4uT5bQzcGiWseZfaEu7Tvw@mail.gmail.com> (raw)
In-Reply-To: <CABCJKueVjP8V-=3Ehi4QvQzg1FZh2unyVMDzSJ_vJ_E5EE+gLg@mail.gmail.com>
On Thu, Nov 14, 2024 at 2:54 AM Sami Tolvanen <samitolvanen@google.com> wrote:
>
> Hi,
>
> On Mon, Nov 11, 2024 at 8:06 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
> >
> > On Thu, Oct 31, 2024 at 2:01 AM Sami Tolvanen <samitolvanen@google.com> wrote:
> > >
> > > To avoid duplication between host programs, move the crc32 code to a
> > > shared header file.
> >
> >
> > Only the motivation to use this long table is to keep compatibility
> > between genksyms and gendwarfksyms.
> > I do not think this should be exposed to other programs.
> >
> >
> > If you avoid the code duplication, you can do
> >
> > // scripts/gendwarfksyms/crc.c
> > #include "../genksyms/crc.c"
>
> Sure, that sounds reasonable. I'll change this in the next version.
BTW, is it necessary to share the same crc function
between genksyms and gendwarfksyms?
If CONFIG_GENKSYMS and CONFIG_GENDWARFKSYMS
were able to produce the same CRC, it would be a good motivation
to share the same function.
However, as far as I tested, gendwarfksyms generates different CRC values.
When a distro migrates to CONFIG_GENDWARFKSYMS,
the new kernel cannot load old modules built with CONFIG_GENKSYMS.
So, there is no need to share the old code.
Another solution might be to use crc32() provided by zlib, for example.
It requires another external library, but this already depends on
libdw and libelf.
>
> > > Suggested-by: Petr Pavlu <petr.pavlu@suse.com>
> > > Signed-off-by: Sami Tolvanen <samitolvanen@google.com>
> > > Acked-by: Neal Gompa <neal@gompa.dev>
> >
> > Does this Ack add any value?
> >
> > Acked-by is meaningful only when it is given by someone who
> > maintains the relevant area or has established a reputation.
> >
> > $ git grep "Neal Gompa"
> > $ git shortlog -n -s | grep "Neal Gompa"
> > 2 Neal Gompa
> >
> > His Ack feels more like "I like it" rather than a qualified endorsement.
>
> Like Neal explained, an Ack from a potential user of this feature
> seemed relevant, but if you don't think it's meaningful, I can
> certainly drop it.
Tested-by is more suitable if he wants to leave something.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2024-11-16 9:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 17:01 [PATCH v5 00/19] Implement DWARF modversions Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 01/19] scripts: move genksyms crc32 implementation to a common include Sami Tolvanen
2024-11-12 4:05 ` Masahiro Yamada
2024-11-13 14:04 ` Neal Gompa
2024-11-13 19:35 ` Luis Chamberlain
2024-11-14 1:08 ` Neal Gompa
2024-11-13 17:53 ` Sami Tolvanen
2024-11-16 9:08 ` Masahiro Yamada [this message]
2024-11-18 21:58 ` Sami Tolvanen
2024-11-19 20:48 ` Darrick J. Wong
2024-11-19 21:37 ` Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 02/19] tools: Add gendwarfksyms Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 03/19] gendwarfksyms: Add address matching Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 04/19] gendwarfksyms: Expand base_type Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 05/19] gendwarfksyms: Add a cache for processed DIEs Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 06/19] gendwarfksyms: Expand type modifiers and typedefs Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 07/19] gendwarfksyms: Expand subroutine_type Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 08/19] gendwarfksyms: Expand array_type Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 09/19] gendwarfksyms: Expand structure types Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 10/19] gendwarfksyms: Limit structure expansion Sami Tolvanen
2024-11-20 21:54 ` Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 11/19] gendwarfksyms: Add die_map debugging Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 12/19] gendwarfksyms: Add symtypes output Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 13/19] gendwarfksyms: Add symbol versioning Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 14/19] gendwarfksyms: Add support for kABI rules Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 15/19] gendwarfksyms: Add support for reserved and ignored fields Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 16/19] gendwarfksyms: Add support for symbol type pointers Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 17/19] export: Add __gendwarfksyms_ptr_ references to exported symbols Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 18/19] kbuild: Add gendwarfksyms as an alternative to genksyms Sami Tolvanen
2024-11-12 4:08 ` Masahiro Yamada
2024-11-13 17:48 ` Sami Tolvanen
2024-10-30 17:01 ` [PATCH v5 19/19] Documentation/kbuild: Add DWARF module versioning Sami Tolvanen
2024-10-30 20:59 ` [PATCH v5 00/19] Implement DWARF modversions Sedat Dilek
2024-10-30 21:14 ` Sami Tolvanen
2024-10-31 1:56 ` Sedat Dilek
2024-10-31 6:18 ` Sedat Dilek
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=CAK7LNARVK1ZpGXZVTAynuo7CDjgB4uT5bQzcGiWseZfaEu7Tvw@mail.gmail.com \
--to=masahiroy@kernel.org \
--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=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=mmaurer@google.com \
--cc=neal@gompa.dev \
--cc=ojeda@kernel.org \
--cc=petr.pavlu@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).