The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] objtool: Fix memory leak in decode_instructions()
Date: Sun, 22 Oct 2017 14:55:56 +0530	[thread overview]
Message-ID: <e5b771a3-568d-8a52-42ae-8c35245a95a4@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171019143226.latzeyhoo3d7dqfo@treble>

On Thursday 19 October 2017 08:02 PM, Josh Poimboeuf wrote:
> On Thu, Oct 19, 2017 at 09:31:37AM -0500, Josh Poimboeuf wrote:
>> On Fri, Oct 13, 2017 at 11:20:58AM +0530, Kamalesh Babulal wrote:
>>> On Friday 13 October 2017 10:36 AM, Josh Poimboeuf wrote:
>>>> On Fri, Oct 13, 2017 at 10:14:36AM +0530, Kamalesh Babulal wrote:
>>>>> On Thursday 12 October 2017 09:40 PM, Josh Poimboeuf wrote:
>>>>>> On Thu, Oct 12, 2017 at 02:32:14PM +0530, Kamalesh Babulal wrote:
>>>>>>> free the allocated insn before returning, when an error occurs
>>>>>>> before adding insn to file->insn_list.
>>>>>>>
>>>>>>> Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
>>>>>>
>>>>>> Any chance you're working on porting objtool to ppc64le? :-)
>>>>>>
>>>>>> Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
>>>>>>
>>>>>
>>>>> Thanks for the review. I have started working on it :)
>>>>
>>>> Good!  Let me know if you have any questions.
>>>
>>> Thank you, I am sure I will have lots of them.
>>>
>>>>
>>>> I originally wrote objtool with arch-independence in mind, though with
>>>> the new "objtool 2.0" rewrite, it unfortunately became more
>>>> x86-specific.
>>>>
>>>> I was hoping to work on making it more arch-independent, and then start
>>>> porting it to other arches, but it may be a few months before I have the
>>>> time to do so.  So any work you want to there would be great.
>>>>
>>>
>>> Sure, will keep that in mind to abstract arch-independent code in to common
>>> files and push arch-dependent code into arch/ directory for both
>>> ppc64le/x86.
>>
>> Kamalesh, since you might be working on this soon, here's a bit of a
>> brain dump in case it helps.
>>
>> I have a vague idea for eventually improving objtool, which might make
>> arch-independence easier.  I wonder if we could use a GCC plugin to add
>> annotations in special sections, which are then read by objtool to help
>> it understand what's going on in the code.
>>
>> I suspect the plugins would need to be arch-specific.  But then maybe
>> that would allow objtool itself to be completely arch-independent.
>> Eventually, if we had similar clang plugins, objtool could become
>> compiler-independent as well.
>>
>> Unfortunately I haven't had a chance to think about it any more deeply
>> than that.  Just something to think about.
>>
>> Or maybe it makes sense to port objtool to ppc first, before trying to
>> abstract the arch-specific parts into plugins.  I dunno.
>>

Thanks for sharing the thoughts on making objtool arch-independent.
I have not followed the discussions closely on GCC plugin to add
annotations/DWARF data. I will read through the ideas, before
commenting on them.


>> Also, another idea that has been suggested, is to use DWARF data as
>> input to objtool.  I have my doubts about that idea, but if it worked,
>> that might be another way to help objtool achieve arch-independence.
>>
>> For a previous discussion of these ideas, see:
>>
>>   https://lkml.kernel.org/r/20170831044209.4hodx2dasad66yab@treble
>
> Also, any chance you'll be in Prague for the conferences next week?  If
> so, we could discuss it more in person.
>

I will not be attending the conference.

-- 
cheers,
Kamalesh.

  reply	other threads:[~2017-10-22  9:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  9:02 [PATCH] objtool: Fix memory leak in decode_instructions() Kamalesh Babulal
2017-10-12 16:10 ` Josh Poimboeuf
2017-10-13  4:44   ` Kamalesh Babulal
2017-10-13  5:06     ` Josh Poimboeuf
2017-10-13  5:50       ` Kamalesh Babulal
2017-10-19 14:31         ` Josh Poimboeuf
2017-10-19 14:32           ` Josh Poimboeuf
2017-10-22  9:25             ` Kamalesh Babulal [this message]
2017-10-19 14:12   ` Josh Poimboeuf
2017-10-19 15:21     ` Ingo Molnar
2017-10-19 15:34       ` Josh Poimboeuf
2017-10-20  7:24         ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2017-10-19 16:27 Josh Poimboeuf

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=e5b771a3-568d-8a52-42ae-8c35245a95a4@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox