linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Abbott Liu <liuwenliang@huawei.com>,
	aryabinin@virtuozzo.com, dvyukov@google.com, corbet@lwn.net,
	christoffer.dall@linaro.org, kstewart@linuxfoundation.org,
	gregkh@linuxfoundation.org, f.fainelli@gmail.com,
	akpm@linux-foundation.org, linux@rasmusvillemoes.dk,
	mawilcox@microsoft.com, pombredanne@nexb.com,
	ard.biesheuvel@linaro.org, vladimir.murzin@arm.com,
	alexander.levin@verizon.com, nicolas.pitre@linaro.org,
	tglx@linutronix.de, thgarnie@google.com, dhowells@redhat.com,
	keescook@chromium.org, arnd@arndb.de, geert@linux-m68k.org,
	tixy@linaro.org, julien.thierry@arm.com, mark.rutland@arm.com,
	james.morse@arm.com, zhichao.huang@linaro.org,
	jinb.park7@gmail.com, labbott@redhat.com, philip@cog.systems,
	grygorii.strashko@linaro.org, catalin.marinas@arm.com,
	opendmb@gmail.com, kirill.shutemov@linux.intel.com,
	kasan-dev@googlegroups.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, linux-mm@kvack.org
Subject: Re: [PATCH v3 2/6] Disable instrumentation for some code
Date: Tue, 3 Apr 2018 12:38:37 +0100	[thread overview]
Message-ID: <20180403113837.GK16141@n2100.armlinux.org.uk> (raw)
In-Reply-To: <7837103a-bcf0-6b00-14d6-bd6b80649886@arm.com>

On Tue, Apr 03, 2018 at 12:30:42PM +0100, Marc Zyngier wrote:
> On 02/04/18 13:04, Abbott Liu wrote:
> > From: Andrey Ryabinin <a.ryabinin@samsung.com>
> > 
> > Disable instrumentation for arch/arm/boot/compressed/*
> > ,arch/arm/kvm/hyp/* and arch/arm/vdso/* because those
> > code won't linkd with kernel image.
> > 
> > Disable kasan check in the function unwind_pop_register
> > because it doesn't matter that kasan checks failed when
> > unwind_pop_register read stack memory of task.
> > 
> > Reviewed-by: Russell King - ARM Linux <linux@armlinux.org.uk>
> > Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> > Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
> 
> Just because I replied to this patch doesn't mean you can stick my
> Reviewed-by tag on it. Please drop this tag until I explicitly say that
> you can add it (see Documentation/process/submitting-patches.rst,
> section 11).
> 
> Same goes for patch 1.

Same goes for that reviewed-by line for me.  From my records, I never
even looked at patch 2 from the first posting, and I don't appear to
have the second posting in my mailbox (it's probably been classed as
spam by dspam.)  So these reviewed-by lines seem to be totally
misleading.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up

  reply	other threads:[~2018-04-03 11:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 12:04 [PATCH v3 0/6] KASan for arm Abbott Liu
2018-04-02 12:04 ` [PATCH v3 1/6] Add TTBR operator for kasan_init Abbott Liu
2018-04-02 12:04 ` [PATCH v3 2/6] Disable instrumentation for some code Abbott Liu
2018-04-03 11:30   ` Marc Zyngier
2018-04-03 11:38     ` Russell King - ARM Linux [this message]
2018-04-02 12:04 ` [PATCH v3 3/6] Replace memory function for kasan Abbott Liu
2018-04-02 12:04 ` [PATCH v3 4/6] Define the virtual space of KASan's shadow region Abbott Liu
2018-04-02 12:04 ` [PATCH v3 5/6] Initialize the mapping of KASan shadow memory Abbott Liu
2018-04-02 18:08   ` Nicolas Pitre
2018-04-02 18:15     ` Russell King - ARM Linux
2018-04-02 18:20       ` Nicolas Pitre
2018-04-02 12:04 ` [PATCH v3 6/6] Enable KASan for arm Abbott Liu
  -- strict thread matches above, loose matches on Subject: below --
2018-04-08  1:38 [PATCH v3 2/6] Disable instrumentation for some code Liuwenliang (Abbott Liu)

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=20180403113837.GK16141@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.levin@verizon.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=aryabinin@virtuozzo.com \
    --cc=catalin.marinas@arm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=corbet@lwn.net \
    --cc=dhowells@redhat.com \
    --cc=dvyukov@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@linaro.org \
    --cc=james.morse@arm.com \
    --cc=jinb.park7@gmail.com \
    --cc=julien.thierry@arm.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=keescook@chromium.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=labbott@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=liuwenliang@huawei.com \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=mawilcox@microsoft.com \
    --cc=nicolas.pitre@linaro.org \
    --cc=opendmb@gmail.com \
    --cc=philip@cog.systems \
    --cc=pombredanne@nexb.com \
    --cc=tglx@linutronix.de \
    --cc=thgarnie@google.com \
    --cc=tixy@linaro.org \
    --cc=vladimir.murzin@arm.com \
    --cc=zhichao.huang@linaro.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;
as well as URLs for NNTP newsgroup(s).