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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 15 Sep 2021 14:19:39 -0700
From:   Linus Torvalds <>
To:     Guenter Roeck <>
Cc:     Richard Henderson <>,
        Ivan Kokshaysky <>,
        Matt Turner <>,
        "James E . J . Bottomley" <>,
        Helge Deller <>,
        "David S . Miller" <>,
        Jakub Kicinski <>,
        alpha <>,
        Geert Uytterhoeven <>,
        Linux Kernel Mailing List <>,, Netdev <>,
        Sparse Mailing-list <>
Subject: Re: [PATCH v2 0/4] Introduce and use absolute_pointer macro

On Wed, Sep 15, 2021 at 12:50 PM Linus Torvalds
<> wrote:
> On Wed, Sep 15, 2021 at 12:47 PM Linus Torvalds
> <> wrote:
> >
> > What other notable issues end up being still live? I sent out that one
> > patch for sparc, but didn't get any response to it. I'm inclined to
> > just apply it (the 'struct mdesc_hdr' pointer misuse one).
> Oh, I forgot about the qnx4 one. That happens on sparc, possibly
> others, but not on x86-64.
> I'll go look at that patch too.

Ok, I didn't love any of the patches I saw for the qnx4 problem, so I
silenced that warning with a new patch of my own. Like the sparc64
case, the fix is to describe more extensively to the compiler what the
code is actually doing.

I think it ended up making it clearer what is going on to humans too.
Although that may be the old "peeing in the snow" effect - it looks
more understandable to me only because I spent so much time trying to
understand what it does, and then wrote the fix based on that possibly
flawed understanding. So of course I find it more understandable.

Looking at the qnx4 code-base history, I don't think it has gotten any
actual development outside of cleanups in the git history timeframe,
which makes me suspect nobody uses this code.

But hey, maybe it just works so well for the very specialized user base ...

Anyway, I pushed it out. I have a clean "allmodconfig" build on all
the architectures I tested, but I didn't test _that_ many.  sparc64,
arm64, powerpc64.

Lots of dts warnings (which aren't fatal), though. Particularly for
the powerpc64 build.


Powered by blists - more mailing lists