From: Peter Zijlstra <peterz@infradead.org>
To: kbuild-all@lists.01.org
Subject: Re: [peterz-queue:core/rcu 31/33] arch/x86/kernel/alternative.c:961:26: error: inlining failed in call to always_inline 'try_get_desc': function attribute mismatch
Date: Thu, 05 Mar 2020 19:47:27 +0100 [thread overview]
Message-ID: <20200305184727.GA3348@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CACT4Y+ZBE=FDMjXxOkmtn0rd8oRWvNaBGnRgXKKSjuohuqd3=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Thu, Mar 05, 2020 at 05:29:27PM +0100, Dmitry Vyukov wrote:
> On Thu, Mar 5, 2020 at 4:55 PM Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Thu, Mar 05, 2020 at 04:23:11PM +0100, Dmitry Vyukov wrote:
> > > Compilers just don't allow this: asking to inline sanitized function
> > > into a non-sanitized function. But I don't know the ptrace/alternative
> > > code good enough to suggest the right alternative (don't call
> > > user_mode, copy user_mode, or something else).
> >
> > Does it work if we inline into a .c file and build it with:
> >
> > KASAN_SANITIZE := n
> > UBSAN_SANITIZE := n
> > KCOV_INSTRUMENT := n
> >
> > Which would be effectively the very same, just more cumbersome.
>
> I think it should work, because then user_mode will also not be instrumented.
Right, but then I have to ask how this is different vs inlining things
into a __no_sanitize function.
Anyway, I'll go move code around so we can do this..
next prev parent reply other threads:[~2020-03-05 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 14:37 [peterz-queue:core/rcu 31/33] arch/x86/kernel/alternative.c:961:26: error: inlining failed in call to always_inline 'try_get_desc': function attribute mismatch kbuild test robot
2020-03-05 13:43 ` Peter Zijlstra
2020-03-05 15:00 ` Dmitry Vyukov
2020-03-05 15:10 ` Dmitry Vyukov
2020-03-05 15:23 ` Dmitry Vyukov
2020-03-05 15:55 ` Peter Zijlstra
2020-03-05 16:29 ` Dmitry Vyukov
2020-03-05 18:47 ` Peter Zijlstra [this message]
2020-03-05 20:13 ` Dmitry Vyukov
2020-03-05 20:28 ` Peter Zijlstra
2020-03-06 5:34 ` Dmitry Vyukov
2020-03-06 9:51 ` Peter Zijlstra
2020-03-06 10:06 ` Dmitry Vyukov
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=20200305184727.GA3348@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kbuild-all@lists.01.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.