linux-kernel - Re: arm32 build warnings in workqueue.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wgGmV6x1brPoROABozj99hrKo031qq8F8K9Mjx2FC6nfw@mail.gmail.com>
Date:   Mon, 31 Jul 2023 12:22:06 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Tejun Heo <tj@...nel.org>
Cc:     Petr Mladek <pmladek@...e.com>, Dave Airlie <airlied@...il.com>,
        Arnd Bergmann <arnd@...db.de>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: arm32 build warnings in workqueue.c

On Mon, 31 Jul 2023 at 12:14, Tejun Heo <tj@...nel.org> wrote:
>
> PAGE_SIZE is easily available through _SC_PAGE_SIZE, so that particular one
> is never a real problem (and a lot of tools have pre-defined helpers for it
> and similarly important constants) but yeah there are other constants which
> I sometimes wish were available through debug info.

We do have that

   scripts/gdb/linux/constants.py.in

thing. Which seems to be the logical place do deal with this all.

That's where other - and arguably much more fundamental - kernel
#define's are dealt with.

Now, looking at the particular constants that are listed, I get the
feeling that the people who have done that script may be mostly
interested in filesystems, but I don't see why it wouldn't be
appropriate for the workstruct stuff too...

                  Linus