From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754850AbcBPKbu (ORCPT ); Tue, 16 Feb 2016 05:31:50 -0500 Received: from e23smtp09.au.ibm.com ([202.81.31.142]:57558 "EHLO e23smtp09.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754795AbcBPKbs (ORCPT ); Tue, 16 Feb 2016 05:31:48 -0500 X-IBM-Helo: d23dlp01.au.ibm.com X-IBM-MailFrom: kamalesh@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org;live-patching@vger.kernel.org Date: Tue, 16 Feb 2016 16:00:30 +0530 From: Kamalesh Babulal To: Torsten Duwe Cc: Petr Mladek , Balbir Singh , Jessica Yu , linux-kernel@vger.kernel.org, Steven Rostedt , Jiri Kosina , live-patching@vger.kernel.org, Miroslav Benes , linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v8 8/8] livepatch: Detect offset for the ftrace location during build Message-ID: <20160216103028.GA10730@linux.vnet.ibm.com> Reply-To: Kamalesh Babulal References: <20160210174221.EBBEC692C8@newverein.lst.de> <20160210174517.8347D692C8@newverein.lst.de> <1455293609.16012.9.camel@gmail.com> <20160212164517.GO12548@pathway.suse.cz> <20160216054701.GA20570@linux.vnet.ibm.com> <20160216082302.GA20522@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20160216082302.GA20522@lst.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16021610-0033-0000-0000-000002F1013E Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Torsten Duwe [2016-02-16 09:23:02]: > On Tue, Feb 16, 2016 at 11:17:02AM +0530, Kamalesh Babulal wrote: > > * Petr Mladek [2016-02-12 17:45:17]: > > > int test(int a) > > > { > > > + printk("%d\n", a); > > > return ++a; > > > } > > > > Thanks. This workaround, helped to load sample livepatch module. > > N.b.: if you try to livepatch/trace such a leaf function without > global dependencies, it will crash if that function got called with > a different TOC value. Hence this whole testing. > I am running out of ideas on how to generate this crash, any pointers will be helpful. > You may alternatively try my gcc patch ;-) Thank you. I will give the patch a try. Regards, Kamalesh