public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Please turn "Cannot use CONFIG_STACK_VALIDATION" into build error
Date: Mon, 13 Feb 2017 14:05:50 -0800	[thread overview]
Message-ID: <20170213220550.GC28220@merlins.org> (raw)
In-Reply-To: <20170213220002.2hqnarjvx3ev2nl3@treble>

On Mon, Feb 13, 2017 at 04:00:02PM -0600, Josh Poimboeuf wrote:
> On Mon, Feb 13, 2017 at 01:31:32PM -0800, Marc MERLIN wrote:
> > Anyway, after not finding it in xconfig, I editted .config, and did:
> > # CONFIG_STACK_VALIDATION is not set
> > save .config
> > and the next build re-enabled the option.
> > That's what caught me by surprise. Did I do something wrong, or is there an
> > issue there?
> 
> I really don't see how it would be possible for it to come back by
> itself, as it's disabled by default, and no other options select it.
> When I remove it, it stays disabled.
 
Mmmh, you are correct.
I have no idea why/how it got re-enabled yesterday. I'm not seeing this
again today.

> > This would help, although in that case you can even make the warning an
> > error since objtool missing seems to be fatal?
> 
> It doesn't need to be fatal though.  It should just be a warning and the
> build should succeed, like it does when building the kernel.

Agreed, that would be even better.

Thanks for looking at that.
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

  reply	other threads:[~2017-02-13 22:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13  8:07 Please turn "Cannot use CONFIG_STACK_VALIDATION" into build error Marc MERLIN
2017-02-13 18:41 ` Josh Poimboeuf
2017-02-13 21:31   ` Marc MERLIN
2017-02-13 22:00     ` Josh Poimboeuf
2017-02-13 22:05       ` Marc MERLIN [this message]
2017-02-13 23:08   ` Jessica Yu
2017-02-14 13:59     ` Josh Poimboeuf
2017-02-14 14:06       ` Josh Poimboeuf

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=20170213220550.GC28220@merlins.org \
    --to=marc@merlins.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@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