All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] coresight: fix kernel panic caused by invalid CPU
Date: Wed, 25 Jan 2017 11:45:03 +0100	[thread overview]
Message-ID: <20170125104503.GA13493@kroah.com> (raw)
In-Reply-To: <1485193284-31636-2-git-send-email-mathieu.poirier@linaro.org>

On Mon, Jan 23, 2017 at 10:41:22AM -0700, Mathieu Poirier wrote:
> From: Wang Nan <wangnan0@huawei.com>
> 
> Commit d52c9750f150 ("coresight: reset "enable_sink" flag when need be")
> caused a kernel panic because of the using of an invalid value: after
> 'for_each_cpu(cpu, mask)', value of local variable 'cpu' become invalid,
> causes following 'cpu_to_node' access invalid memory area.

You should add a "Fixes:" tag when you write something like this, as you
have all of the information here. I'll add it, and the stable tag as
well...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] coresight: fix kernel panic caused by invalid CPU
Date: Wed, 25 Jan 2017 11:45:03 +0100	[thread overview]
Message-ID: <20170125104503.GA13493@kroah.com> (raw)
In-Reply-To: <1485193284-31636-2-git-send-email-mathieu.poirier@linaro.org>

On Mon, Jan 23, 2017 at 10:41:22AM -0700, Mathieu Poirier wrote:
> From: Wang Nan <wangnan0@huawei.com>
> 
> Commit d52c9750f150 ("coresight: reset "enable_sink" flag when need be")
> caused a kernel panic because of the using of an invalid value: after
> 'for_each_cpu(cpu, mask)', value of local variable 'cpu' become invalid,
> causes following 'cpu_to_node' access invalid memory area.

You should add a "Fixes:" tag when you write something like this, as you
have all of the information here. I'll add it, and the stable tag as
well...

thanks,

greg k-h

  reply	other threads:[~2017-01-25 10:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 17:41 [PATCH 0/3] coresight: next v4.10-rc5 Mathieu Poirier
2017-01-23 17:41 ` Mathieu Poirier
2017-01-23 17:41 ` [PATCH 1/3] coresight: fix kernel panic caused by invalid CPU Mathieu Poirier
2017-01-23 17:41   ` Mathieu Poirier
2017-01-25 10:45   ` Greg KH [this message]
2017-01-25 10:45     ` Greg KH
2017-01-23 17:41 ` [PATCH 2/3] coresight: etm4x: Fix enabling of cycle accurate tracing in perf Mathieu Poirier
2017-01-23 17:41   ` Mathieu Poirier
2017-01-23 17:41 ` [PATCH 3/3] coresight: etm4x: Fix timestamp configuration when working from perf Mathieu Poirier
2017-01-23 17:41   ` Mathieu Poirier

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=20170125104503.GA13493@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.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 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.