Jiri Kosina writes:
> On Wed, 30 Jan 2019, Michael Ellerman wrote:
>
>> I'm happy to take it, unless there's some reason you'd rather it go via
>> the LP tree?
>
> As this is more about reliable stack unwinding than live patching per se
> (which is only a user of that facility), I'd actually
On Wed, 30 Jan 2019, Michael Ellerman wrote:
> I'm happy to take it, unless there's some reason you'd rather it go via
> the LP tree?
As this is more about reliable stack unwinding than live patching per se
(which is only a user of that facility), I'd actually slightly prefer if
it goes via
Jiri Kosina writes:
> On Tue, 22 Jan 2019, Joe Lawrence wrote:
>
>> This patchset fixes a false negative report (ie, unreliable) from the
>> ppc64 reliable stack unwinder, discussed here [1] when it may
>> inadvertently trip over a stale exception marker left on the stack.
>>
>> The first two
On Tue, 22 Jan 2019, Joe Lawrence wrote:
> This patchset fixes a false negative report (ie, unreliable) from the
> ppc64 reliable stack unwinder, discussed here [1] when it may
> inadvertently trip over a stale exception marker left on the stack.
>
> The first two patches fix this bug.
On Tue, Jan 22, 2019 at 10:57:20AM -0500, Joe Lawrence wrote:
> This patchset fixes a false negative report (ie, unreliable) from the
> ppc64 reliable stack unwinder, discussed here [1] when it may
> inadvertently trip over a stale exception marker left on the stack.
>
> The first two patches fix
This patchset fixes a false negative report (ie, unreliable) from the
ppc64 reliable stack unwinder, discussed here [1] when it may
inadvertently trip over a stale exception marker left on the stack.
The first two patches fix this bug. Nicolai's change clears the marker
from the stack when an
