From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2017-09-07 06:35:56
Otherwise we end up not yet having computed the right
diag data size on powernv where EEH initialization
is delayed, thus causing memory corruption later on
when calling OPAL.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/powerpc/kernel/eeh.c | 4 ++++
arch/powerpc/kernel/eeh_dev.c | 18 ------------------
2 files changed, 4 insertions(+), 18 deletions(-)
From: Russell Currey <hidden> Date: 2017-09-14 01:18:20
On Thu, 2017-09-07 at 16:35 +1000, Benjamin Herrenschmidt wrote:
Otherwise we end up not yet having computed the right
diag data size on powernv where EEH initialization
is delayed, thus causing memory corruption later on
when calling OPAL.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2017-09-20 10:59:09
Benjamin Herrenschmidt [off-list ref] writes:
Otherwise we end up not yet having computed the right
diag data size on powernv where EEH initialization
is delayed, thus causing memory corruption later on
when calling OPAL.
When did this break? Do we have a commit we can tag with Fixes: ?
Stable?
I assume we want to merge this ASAP as a fix, I think I can safely take
this without patch 2?
cheers
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2017-09-20 13:00:13
On Wed, 2017-09-20 at 20:59 +1000, Michael Ellerman wrote:
Benjamin Herrenschmidt [off-list ref] writes:
quoted
Otherwise we end up not yet having computed the right
diag data size on powernv where EEH initialization
is delayed, thus causing memory corruption later on
when calling OPAL.
When did this break? Do we have a commit we can tag with Fixes: ?
Stable?
I assume we want to merge this ASAP as a fix, I think I can safely take
this without patch 2?
Russell, can you help Michael with that ? I don't even remember what's
in patch 2 :)
Cheers,
Ben.
From: Russell Currey <hidden> Date: 2017-09-21 02:20:09
On Wed, 2017-09-20 at 20:59 +1000, Michael Ellerman wrote:
Benjamin Herrenschmidt [off-list ref] writes:
quoted
Otherwise we end up not yet having computed the right
diag data size on powernv where EEH initialization
is delayed, thus causing memory corruption later on
when calling OPAL.
When did this break? Do we have a commit we can tag with Fixes: ?
Stable?
I assume we want to merge this ASAP as a fix, I think I can safely take
this without patch 2?
cheers
Yes it should be merged ASAP as a fix, and fixes
5cb1f8fdddb7475f38ea9fba48da17c002eec90b.
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2017-09-21 04:57:50
Russell Currey [off-list ref] writes:
On Wed, 2017-09-20 at 20:59 +1000, Michael Ellerman wrote:
quoted
Benjamin Herrenschmidt [off-list ref] writes:
quoted
Otherwise we end up not yet having computed the right
diag data size on powernv where EEH initialization
is delayed, thus causing memory corruption later on
when calling OPAL.
When did this break? Do we have a commit we can tag with Fixes: ?
Stable?
I assume we want to merge this ASAP as a fix, I think I can safely take
this without patch 2?
cheers
Yes it should be merged ASAP as a fix, and fixes
5cb1f8fdddb7475f38ea9fba48da17c002eec90b.
From: Michael Ellerman <hidden> Date: 2017-09-22 01:03:33
On Thu, 2017-09-07 at 06:35:40 UTC, Benjamin Herrenschmidt wrote:
Otherwise we end up not yet having computed the right
diag data size on powernv where EEH initialization
is delayed, thus causing memory corruption later on
when calling OPAL.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: Russell Currey <redacted>