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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191107114553.GA6159@sirena.co.uk>
Date:   Thu, 7 Nov 2019 11:45:53 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Robin Murphy <robin.murphy@....com>,
        Naresh Kamboju <naresh.kamboju@...aro.org>,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Arnd Bergmann <arnd@...db.de>,
        open list <linux-kernel@...r.kernel.org>,
        lkft-triage@...ts.linaro.org, John Stultz <john.stultz@...aro.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: Linux-next-20191106 : arm64: Internal error: Oops: 96000007

On Thu, Nov 07, 2019 at 09:00:25AM +0100, Linus Walleij wrote:

> I wonder if it's worth to look at the static checkers like checkpatch
> to warn for this?

I noticed this due to the warning emitted in the build process so I'm
not sure there'd be much more chance that people would notice (though
admittedly the warning during the build doesn't suggest a boot problem).
There's hundreds of other examples in the tree that don't trigger
crashes for whatever reason, I think this one was just noticable because
it got built in.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ