From: Balbir Singh <bsingharora@gmail.com>
To: "Naveen N . Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/livepatch: Fix livepatch stack access
Date: Fri, 29 Sep 2017 21:47:19 +1000 [thread overview]
Message-ID: <1506685639.7352.0.camel@gmail.com> (raw)
In-Reply-To: <20170920111108.wptb7ifdbqk4ndvm@naverao1-tp.localdomain>
On Wed, 2017-09-20 at 16:41 +0530, Naveen N . Rao wrote:
> On 2017/09/20 03:49PM, Kamalesh Babulal wrote:
> > While running stress test with livepatch module loaded, kernel
> > bug was triggered.
> >
> > cpu 0x5: Vector: 400 (Instruction Access) at [c0000000eb9d3b60]
> > pc: c0000000eb9d3e30
> > lr: c0000000eb9d3e30
> > sp: c0000000eb9d3de0
> > msr: 800000001280b033
> > current = 0xc0000000dbd38700
> > paca = 0xc00000000fe01400 softe: 0 irq_happened: 0x01
> > pid = 8618, comm = make
> > Linux version 4.13.0+ (root@ubuntu) (gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)) #1 SMP Wed Sep 13 03:49:27 EDT 2017
> >
> > 5:mon> t
> > [c0000000eb9d3de0] c0000000eb9d3e30 (unreliable)
> > [c0000000eb9d3e30] c000000000008ab4 hardware_interrupt_common+0x114/0x120
> > --- Exception: 501 (Hardware Interrupt) at c000000000053040 livepatch_handler+0x4c/0x74
> > [c0000000eb9d4120] 0000000057ac6e9d (unreliable)
> > [d0000000089d9f78] 2e0965747962382e
> > SP (965747962342e09) is in userspace
> >
> > When an interrupt is served in between the livepatch_handler execution,
> > there are chances of the livepatch_stack/task task getting corrupted.
> >
> > CPU 1
> > =============
> > Task A Interrupt Handler
> > ========= =================
> > livepatch_handler:
> > mr r0, r1
> > ld r1, TI_livepatch_sp(r12)
> > hardware_interrupt_common
> > |_do_IRQ
> > |_ call_do_irq:
> > mflr r0
> > std r0,16(r1)
> > stdu r1,THREAD_SIZE-STACK_FRAME_OVERHEAD(r4)
> > ...
> > lis r2, STACK_END_MAGIC@h
> > ori r2, r2, STACK_END_MAGIC@l
> > ld r12, -8(r1) <- livepatch stack is corrupted.
> >
> > Fix the corruption by using r11 register for livepatch stack manipulation,
> > instead of shuffling task stack and livepatch stack into r1 register.
> > Using r11 register also avoids disabling/enabling irq's while setting
> > up the livepatch stack.
> >
> > Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
> > Cc: Balbir Singh <bsingharora@gmail.com>
> > Cc: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
> > Cc: linuxppc-dev@lists.ozlabs.org
> > ---
> > arch/powerpc/kernel/trace/ftrace_64_mprofile.S | 45 +++++++++-----------------
> > 1 file changed, 15 insertions(+), 30 deletions(-)
>
> Reviewed-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Reviewed-by: Balbir Singh <bsingharora@gmail.com>
next prev parent reply other threads:[~2017-09-29 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 10:19 [PATCH] powerpc/livepatch: Fix livepatch stack access Kamalesh Babulal
2017-09-20 11:11 ` Naveen N . Rao
2017-09-29 11:47 ` Balbir Singh [this message]
2017-09-21 10:02 ` Michael Ellerman
2017-09-21 11:00 ` Balbir Singh
2017-09-21 11:53 ` Kamalesh Babulal
2017-09-21 16:55 ` Naveen N . Rao
2017-09-22 5:16 ` Kamalesh Babulal
2017-10-12 0:20 ` Michael Ellerman
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=1506685639.7352.0.camel@gmail.com \
--to=bsingharora@gmail.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
/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).