All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Nick Desaulniers <nick.desaulniers@gmail.com>
Cc: Matthias Kaehlcke <mka@chromium.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Manoj Gupta <manojgupta@chromium.org>,
	AlistairStrachan <astrachan@google.com>,
	"Steven Rostedt (VMware)" <rostedt@goodmis.org>
Subject: Re: Clang patch stacks for LTS kernels (v4.4 and v4.9) and status update
Date: Tue, 22 May 2018 09:11:54 +0200	[thread overview]
Message-ID: <CA+icZUWjKDgg+-EJ8dyw-r4A+O_iMLPEBk2aKhTWO9_0Em_s4A@mail.gmail.com> (raw)
In-Reply-To: <CAH7mPviH3EiozBxkdZ685ZOo1bNJLLaOPFYwbn2NvD77w=P3Aw@mail.gmail.com>

On Sat, May 19, 2018 at 12:54 AM, Nick Desaulniers
<nick.desaulniers@gmail.com> wrote:
> Sedat,
> Thanks for the report.  We have a fix ready in
> https://bugs.llvm.org/show_bug.cgi?id=37512.  Can you report what
> version of clang you were using and if earlier versions of clang have
> this issue?
> Thanks,

Hi Nick,

yesterday was public holiday in Germany, so I answer today.

These are really good news, Thanks.

For my recent experiments with Linux-kernel v4.14.y LTS I used Clang...

#1: version 6.0 from Debian/testing repositories
#2: version 7 (svn330207) from <apt-llvm.org>

In these cases I had success (good means boot on bare metal) or it
failed (bad verified in Qemu):

bad: CONFIG_PARAVIRT=y and  CONFIG_CC_STACKPROTECTOR_STRONG=y
good: CONFIG_PARAVIRT=n and CONFIG_CC_STACKPROTECTOR_STRONG=y
good: CONFIG_PARAVIRT=y and CONFIG_CC_STACKPROTECTOR_NONE=y

So, the issue is in both Clang versions and I appreciate to have your
fix in LLVM/Clang version 6.0.1 as I don't know which version will get
into upcoming Debian/buster (version 10, current status: testing).

Hope this helps.

Regards,
- Sedat -

  reply	other threads:[~2018-05-22  7:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 13:56 Clang patch stacks for LTS kernels (v4.4 and v4.9) and status update Sedat Dilek
2018-04-23 17:42 ` Matthias Kaehlcke
2018-04-24 11:54   ` Sedat Dilek
2018-04-24 23:06     ` Matthias Kaehlcke
2018-05-06  7:42       ` Sedat Dilek
2018-05-06  8:16         ` Sedat Dilek
2018-05-07 17:49         ` Matthias Kaehlcke
2018-05-07 19:37           ` Sedat Dilek
2018-05-11 11:52           ` Sedat Dilek
2018-05-18 22:54             ` Nick Desaulniers
2018-05-22  7:11               ` Sedat Dilek [this message]
2018-05-22  7:39               ` Sedat Dilek
2018-05-22  8:04                 ` Sedat Dilek
2018-05-22  8:49                   ` Sedat Dilek
2018-05-22 10:16                     ` Sedat Dilek
2018-05-22 12:05                       ` Sedat Dilek
2018-05-22 12:17                         ` Sedat Dilek
2018-05-22 14:55                           ` Sedat Dilek
2018-05-06  6:35   ` Sedat Dilek
2018-05-06  7:41     ` Dmitry Vyukov
2018-05-06  7:58       ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2017-08-22 23:13 Matthias Kaehlcke

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=CA+icZUWjKDgg+-EJ8dyw-r4A+O_iMLPEBk2aKhTWO9_0Em_s4A@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=arnd@arndb.de \
    --cc=astrachan@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manojgupta@chromium.org \
    --cc=mka@chromium.org \
    --cc=nick.desaulniers@gmail.com \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.