From: Nick Desaulniers <ndesaulniers@google.com>
To: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Tri Vo <trong@android.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Greg Hackmann <ghackmann@android.com>,
Linux Memory Management List <linux-mm@kvack.org>,
kbuild-all@01.org, Randy Dunlap <rdunlap@infradead.org>,
kbuild test robot <lkp@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] gcov: fix when CONFIG_MODULES is not set
Date: Fri, 5 Apr 2019 10:18:26 -0700 [thread overview]
Message-ID: <CAKwvOdnJLOCKXZQcrCrsM1j5b4U_0vdV7JhbDtBUdLe3cMYp4A@mail.gmail.com> (raw)
In-Reply-To: <20190403152719.GH22763@bombadil.infradead.org>
On Wed, Apr 3, 2019 at 8:27 AM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Tue, Apr 02, 2019 at 10:09:56AM +0700, trong@android.com wrote:
> > From: Tri Vo <trong@android.com>
> >
> > Fixes: 8c3d220cb6b5 ("gcov: clang support")
>
> I think this is the wrong fix. Why not simply:
I spoke with Tri quickly about this proposal and we agree it's a better fix.
Andrew, would you mind dropping:
https://ozlabs.org/~akpm/mmotm/broken-out/gcov-clang-support-fix.patch
?
Matthew, would you please send that patch with a commit message? Or
if you would prefer us to send with your suggested-by tag, we can do
that, too. Whichever you prefer, please let me know. Thanks for the
suggestion.
>
> +++ b/include/linux/module.h
> @@ -709,6 +709,11 @@ static inline bool is_module_text_address(unsigned long addr)
> return false;
> }
>
> +static inline bool within_module(unsigned long addr, const struct module *mod)
> +{
> + return false;
> +}
> +
> /* Get/put a kernel symbol (calls should be symmetric) */
> #define symbol_get(x) ({ extern typeof(x) x __attribute__((weak)); &(x); })
> #define symbol_put(x) do { } while (0)
>
--
Thanks,
~Nick Desaulniers
prev parent reply other threads:[~2019-04-05 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 3:09 trong
2019-04-02 4:47 ` Randy Dunlap
2019-04-03 15:27 ` Matthew Wilcox
2019-04-05 17:18 ` Nick Desaulniers [this message]
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=CAKwvOdnJLOCKXZQcrCrsM1j5b4U_0vdV7JhbDtBUdLe3cMYp4A@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=akpm@linux-foundation.org \
--cc=ghackmann@android.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oberpar@linux.ibm.com \
--cc=rdunlap@infradead.org \
--cc=trong@android.com \
--cc=willy@infradead.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