All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morse <james.morse@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] PM / Hibernate: Don't let kasan instrument snapshot.c
Date: Wed, 15 Jun 2016 11:25:18 +0100	[thread overview]
Message-ID: <57612D0E.5050209@arm.com> (raw)
In-Reply-To: <7230305.BYjCFel4WC@vostro.rjw.lan>

Hi Rafael,

On 15/06/16 00:26, Rafael J. Wysocki wrote:
> Does the arch code need to be annotated in a similar way too?

Only if you do the restore copying from C, both 32bit and 64bit x86 do this copy
in assembly code, which doesn't get instrumented.


Thanks,

James

WARNING: multiple messages have this Message-ID (diff)
From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM / Hibernate: Don't let kasan instrument snapshot.c
Date: Wed, 15 Jun 2016 11:25:18 +0100	[thread overview]
Message-ID: <57612D0E.5050209@arm.com> (raw)
In-Reply-To: <7230305.BYjCFel4WC@vostro.rjw.lan>

Hi Rafael,

On 15/06/16 00:26, Rafael J. Wysocki wrote:
> Does the arch code need to be annotated in a similar way too?

Only if you do the restore copying from C, both 32bit and 64bit x86 do this copy
in assembly code, which doesn't get instrumented.


Thanks,

James

  reply	other threads:[~2016-06-15 10:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 12:20 [PATCH] PM / Hibernate: Don't let kasan instrument snapshot.c James Morse
2016-06-02 12:20 ` James Morse
2016-06-14 23:26 ` Rafael J. Wysocki
2016-06-14 23:26   ` Rafael J. Wysocki
2016-06-15 10:25   ` James Morse [this message]
2016-06-15 10:25     ` James Morse
2016-06-16  1:22     ` Rafael J. Wysocki
2016-06-16  1:22       ` Rafael J. Wysocki

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=57612D0E.5050209@arm.com \
    --to=james.morse@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    /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.