From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: akpm@linux-foundation.org
Cc: andreyknvl@gmail.com, arnd@arndb.de, ast@kernel.org,
benh@kernel.crashing.org, bp@alien8.de,
christophe.leroy@csgroup.eu, davem@davemloft.net,
dvyukov@google.com, glider@google.com, ink@jurassic.park.msu.ru,
mattst88@gmail.com, mingo@redhat.com, mm-commits@vger.kernel.org,
monstr@monstr.eu, mpe@ellerman.id.au, paulus@samba.org,
pmladek@suse.com, rostedt@goodmis.org, rth@twiddle.net,
ryabinin.a.a@gmail.com, senozhatsky@chromium.org,
tglx@linutronix.de, wangkefeng.wang@huawei.com
Subject: Re: + kallsyms-remove-arch-specific-text-and-data-check.patch added to -mm tree
Date: Fri, 1 Oct 2021 09:47:59 +0900 [thread overview]
Message-ID: <YVZav3rnb3+A9bHz@google.com> (raw)
In-Reply-To: <20210930212149.TDvMQI9fl%akpm@linux-foundation.org>
On (21/09/30 14:21), akpm@linux-foundation.org wrote:
> +++ a/include/linux/kallsyms.h
> @@ -34,8 +34,7 @@ static inline int is_kernel_inittext(uns
>
> static inline int is_kernel_text(unsigned long addr)
> {
> - if ((addr >= (unsigned long)_stext && addr <= (unsigned long)_etext) ||
> - arch_is_kernel_text(addr))
> + if ((addr >= (unsigned long)_stext && addr <= (unsigned long)_etext))
> return 1;
Does this need to include _etext or should it be '< _etext'?
next prev parent reply other threads:[~2021-10-01 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 21:21 + kallsyms-remove-arch-specific-text-and-data-check.patch added to -mm tree akpm
2021-10-01 0:47 ` Sergey Senozhatsky [this message]
2021-10-01 0:55 ` Sergey Senozhatsky
2021-10-01 1:20 ` Sergey Senozhatsky
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=YVZav3rnb3+A9bHz@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=arnd@arndb.de \
--cc=ast@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mingo@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=rth@twiddle.net \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.com \
/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.