All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 18 (objtool)
Date: Thu, 26 Mar 2020 11:36:10 -0700	[thread overview]
Message-ID: <202003261133.814BEE9F@keescook> (raw)
In-Reply-To: <20200326163110.n35lxcgkfcar7vd5@treble>

On Thu, Mar 26, 2020 at 11:31:10AM -0500, Josh Poimboeuf wrote:
> On Wed, Mar 25, 2020 at 10:57:02PM -0700, Kees Cook wrote:
> > > In the meantime I can still change objtool to ignore unreachable UD2s if
> > > there aren't any better ideas.
> > 
> > It'll still need the objtool change for CONFIG_UBSAN_TRAP, though based on
> > the clang bug discussion, I'll probably _also_ be adding CONFIG_UBSAN_WARN
> > which won't have an unreachable (and won't bloat the kernel). Testing
> > still under way... it is possible that CONFIG_UBSAN_TRAP will go away
> > in the future, though. If that happens, should I also remove the change
> > at that time?
> 
> I'll go ahead and make the patch and post it soon.  It should be pretty
> trivial.  We can always revert it if CONFIG_UBSAN_TRAP goes away.

Awesome, thanks very much. After digging into the WARN-style option,
it seems that TRAP is unlikely to go away because it's Clang only;
GCC doesn't support the "minimal runtime" option. Yay compilers.

Anyway, I'll still get the WARN mode sent out. Thanks for looking at this;
can you CC me on the patch? I'm trying to get more familiar with objtool
so I don't have to bug you when objtool is angered by crazy stuff I do. ;)

-- 
Kees Cook

  reply	other threads:[~2020-03-26 18:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 11:09 linux-next: Tree for Mar 18 Stephen Rothwell
2020-03-18 16:14 ` linux-next: Tree for Mar 18 (drivers/base/power/sysfs.c) Randy Dunlap
2020-03-19  3:20   ` Stephen Rothwell
2020-03-19 14:47     ` [PATCH net-next] sysfs: fix static inline declaration of sysfs_groups_change_owner() Christian Brauner
2020-03-19 16:19       ` Randy Dunlap
2020-03-20  4:17       ` David Miller
2020-03-18 16:48 ` linux-next: Tree for Mar 18 (objtool) Randy Dunlap
2020-03-18 16:55   ` Josh Poimboeuf
2020-03-18 18:23   ` Josh Poimboeuf
2020-03-18 20:05     ` Peter Zijlstra
2020-03-19 11:12       ` Peter Zijlstra
2020-03-19 17:31       ` Josh Poimboeuf
2020-03-19 17:33         ` Josh Poimboeuf
2020-03-19 17:40           ` Josh Poimboeuf
2020-03-19 17:45             ` Josh Poimboeuf
2020-03-20  8:26               ` Peter Zijlstra
2020-03-20 18:35                 ` Kees Cook
2020-03-24 16:44                   ` Josh Poimboeuf
2020-03-24 18:18                     ` Kees Cook
2020-03-24 22:24                       ` Josh Poimboeuf
2020-03-26  5:57                         ` Kees Cook
2020-03-26 16:31                           ` Josh Poimboeuf
2020-03-26 18:36                             ` Kees Cook [this message]
2020-03-27  3:55                               ` 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=202003261133.814BEE9F@keescook \
    --to=keescook@chromium.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.