From: Jarkko Sakkinen <jarkko@kernel.org>
To: lkp@lists.01.org
Subject: Re: [PATCH] objtool, static_call: Don't emit static_call_site for .exit.text
Date: Wed, 17 Mar 2021 23:55:54 +0200 [thread overview]
Message-ID: <YFJ66nW0vabAgGqm@kernel.org> (raw)
In-Reply-To: <CAFA6WYNr8SR=20LKJD0+AyrVXLY2CqQPqRE_60EestYv9L5AcA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
On Wed, Mar 17, 2021 at 07:07:07PM +0530, Sumit Garg wrote:
> On Wed, 17 Mar 2021 at 18:16, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Wed, Mar 17, 2021 at 05:25:48PM +0530, Sumit Garg wrote:
> > > Thanks Peter for this fix. It does work for me on qemu for x86. Can
> > > you turn this into a proper fix patch? BTW, feel free to add:
> >
> > Per the below, the original patch ought to be fixed as well, to not use
> > static_call() in __exit.
>
> Okay, fair enough.
>
> Jarkko,
>
> Can you please incorporate the following change to the original patch as well?
Can you roll-out a proper patch of this?
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Oliver Sang <oliver.sang@intel.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
jbaron@akamai.com, lkp@lists.01.org,
kbuild test robot <lkp@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] objtool,static_call: Don't emit static_call_site for .exit.text
Date: Wed, 17 Mar 2021 23:55:54 +0200 [thread overview]
Message-ID: <YFJ66nW0vabAgGqm@kernel.org> (raw)
In-Reply-To: <CAFA6WYNr8SR=20LKJD0+AyrVXLY2CqQPqRE_60EestYv9L5AcA@mail.gmail.com>
On Wed, Mar 17, 2021 at 07:07:07PM +0530, Sumit Garg wrote:
> On Wed, 17 Mar 2021 at 18:16, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Wed, Mar 17, 2021 at 05:25:48PM +0530, Sumit Garg wrote:
> > > Thanks Peter for this fix. It does work for me on qemu for x86. Can
> > > you turn this into a proper fix patch? BTW, feel free to add:
> >
> > Per the below, the original patch ought to be fixed as well, to not use
> > static_call() in __exit.
>
> Okay, fair enough.
>
> Jarkko,
>
> Can you please incorporate the following change to the original patch as well?
Can you roll-out a proper patch of this?
/Jarkko
next prev parent reply other threads:[~2021-03-17 21:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 14:23 [KEYS] 4a00e5e212: WARNING:at_arch/x86/kernel/static_call.c:#__static_call_validate kernel test robot
2021-03-16 8:04 ` Sumit Garg
2021-03-17 3:01 ` Oliver Sang
2021-03-17 7:25 ` Sumit Garg
2021-03-17 8:41 ` Peter Zijlstra
2021-03-17 8:59 ` Peter Zijlstra
2021-03-17 9:02 ` Peter Zijlstra
2021-03-17 11:55 ` Sumit Garg
2021-03-17 12:45 ` [PATCH] objtool, static_call: Don't emit static_call_site for .exit.text Peter Zijlstra
2021-03-17 12:45 ` [PATCH] objtool,static_call: " Peter Zijlstra
2021-03-17 13:37 ` [PATCH] objtool, static_call: " Sumit Garg
2021-03-17 13:37 ` [PATCH] objtool,static_call: " Sumit Garg
2021-03-17 21:55 ` Jarkko Sakkinen [this message]
2021-03-17 21:55 ` Jarkko Sakkinen
2021-03-18 4:42 ` [PATCH] objtool, static_call: " Sumit Garg
2021-03-18 4:42 ` [PATCH] objtool,static_call: " Sumit Garg
2021-03-17 21:01 ` [PATCH] objtool, static_call: " Jarkko Sakkinen
2021-03-17 21:01 ` [PATCH] objtool,static_call: " Jarkko Sakkinen
2021-03-18 0:02 ` [PATCH] objtool, static_call: " Josh Poimboeuf
2021-03-18 0:02 ` [PATCH] objtool,static_call: " Josh Poimboeuf
2021-03-18 7:59 ` [PATCH] objtool, static_call: " Peter Zijlstra
2021-03-18 7:59 ` [PATCH] objtool,static_call: " Peter Zijlstra
2021-03-18 8:30 ` [PATCH] objtool, static_call: " Peter Zijlstra
2021-03-18 8:30 ` [PATCH] objtool,static_call: " Peter Zijlstra
2021-03-18 8:47 ` [PATCH] objtool, static_call: " Peter Zijlstra
2021-03-18 8:47 ` [PATCH] objtool,static_call: " Peter Zijlstra
2021-03-17 21:00 ` [KEYS] 4a00e5e212: WARNING:at_arch/x86/kernel/static_call.c:#__static_call_validate Jarkko Sakkinen
2021-03-18 10:25 ` Peter Zijlstra
2021-03-18 11:03 ` Sumit Garg
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=YFJ66nW0vabAgGqm@kernel.org \
--to=jarkko@kernel.org \
--cc=lkp@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.