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: <20170604.162226.1986766921223996448.davem@davemloft.net>
Date:   Sun, 04 Jun 2017 16:22:26 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     wbx@...nadk.org
Cc:     glaubitz@...sik.fu-berlin.de, linux-kernel@...r.kernel.org,
        sparclinux@...r.kernel.org
Subject: Re: sparc gcc 7.1 compile issue

From: Waldemar Brodkorb <wbx@...nadk.org>
Date: Sun, 4 Jun 2017 16:40:45 +0200

> Hi Adrian,
> John Paul Adrian Glaubitz wrote,
> 
>> On 06/02/2017 07:28 PM, David Miller wrote:
>> >> Isn't a bug in the kernel if an application is able to crash to the point
>> >> that the machine has to be hard-rebooted?
>> > 
>> > It can be a bug in the compiler too and not necessarily the kernel's
>> > fault which is what I think is happening in your case.
>> 
>> So, in your point of view it's perfectly fine if an application is able
>> to crash the whole kernel with just user privileges?
>> 
>> Shouldn't the kernel be able to cope with that?
> 
> I think he means your kernel you are running might be miscompiled
> with gcc 7.1.

That's exactly what I am saying.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ