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:   Sun, 4 Jun 2017 16:40:45 +0200
From:   Waldemar Brodkorb <>
To:     John Paul Adrian Glaubitz <>
Cc:     David Miller <>,,,
Subject: Re: sparc gcc 7.1 compile issue

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.

What kernel version you are running? Which compiler you used to
generate the running kernel? If it is gcc 7.1, what is if you try to
reproduce the crash with the same kernel version compiled with gcc
Wouldn't this show if it is a compiler or kernel bug?

best regards

Powered by blists - more mailing lists