public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: David Miller <davem@davemloft.net>,
	wbx@openadk.org, linux-kernel@vger.kernel.org,
	sparclinux@vger.kernel.org
Subject: Re: sparc gcc 7.1 compile issue
Date: Sun, 4 Jun 2017 16:40:45 +0200	[thread overview]
Message-ID: <20170604144044.GK26922@waldemar-brodkorb.de> (raw)
In-Reply-To: <a2f74c42-5a3a-23ec-b8f9-7694f606b714@physik.fu-berlin.de>

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
6.3?
Wouldn't this show if it is a compiler or kernel bug?

best regards
 Waldemar

  reply	other threads:[~2017-06-04 14:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31 19:34 sparc gcc 7.1 compile issue Waldemar Brodkorb
2017-05-31 21:10 ` David Miller
2017-06-01 12:12   ` Waldemar Brodkorb
2017-06-01 12:46     ` Anatoly Pugachev
2017-06-01 12:48       ` John Paul Adrian Glaubitz
2017-06-01 16:45       ` David Miller
2017-06-02  9:17   ` John Paul Adrian Glaubitz
2017-06-02 14:22     ` David Miller
2017-06-02 16:33       ` John Paul Adrian Glaubitz
2017-06-02 17:28         ` David Miller
2017-06-04 13:16           ` John Paul Adrian Glaubitz
2017-06-04 14:40             ` Waldemar Brodkorb [this message]
2017-06-04 15:09               ` John Paul Adrian Glaubitz
2017-06-04 20:22               ` David Miller
2017-06-04 20:27                 ` John Paul Adrian Glaubitz
2017-06-04 20:21             ` David Miller
2017-06-04 20:26               ` John Paul Adrian Glaubitz
2017-06-04 20:30                 ` David Miller
2017-06-04 20:33                   ` John Paul Adrian Glaubitz
2017-06-04 20:34                     ` David Miller
2017-06-04 20:38                       ` John Paul Adrian Glaubitz
2017-06-18  9:22   ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170604144044.GK26922@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=davem@davemloft.net \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox