mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kieran Bingham <kbingham@kernel.org>,
	Xi Kangjie <imxikangjie@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/gdb: fix get_thread_info
Date: Thu, 18 Jan 2018 16:50:21 +0100	[thread overview]
Message-ID: <273f82e8-7419-a636-c7d3-a0857b478ade@siemens.com> (raw)
In-Reply-To: <782503b9-83fc-6a47-24ba-524a728da642@kernel.org>

On 2018-01-18 16:47, Kieran Bingham wrote:
> 
> On 18/01/18 15:43, Jan Kiszka wrote:
>> On 2018-01-18 22:01, Xi Kangjie wrote:
>>> Since kernel 4.9, the thread_info has been moved into task_struct,
>>> no longer locates at the bottom of kernel stack.
>>>
>>> See commits:
>>> - commit c65eacbe290b ("sched/core: Allow putting thread_info into
>>> task_struct")
>>> - commit 15f4eae70d36 ("x86: Move thread_info into task_struct")
>>>
>>> Before fix:
>>> (gdb) set $current = $lx_current()
>>> (gdb) p $lx_thread_info($current)
>>> $1 = {flags = 1470918301}
>>> (gdb) p $current.thread_info
>>> $2 = {flags = 2147483648}
>>>
>>> After fix:
>>> (gdb) p $lx_thread_info($current)
>>> $1 = {flags = 2147483648}
>>> (gdb) p $current.thread_info
>>> $2 = {flags = 2147483648}
>>>
>>> Signed-off-by: Xi Kangjie <imxikangjie@gmail.com>
>>> ---
>>>  scripts/gdb/linux/tasks.py | 2 ++
>>>  1 file changed, 2 insertions(+)
>>>
>>> diff --git a/scripts/gdb/linux/tasks.py b/scripts/gdb/linux/tasks.py
>>> index 1bf949c43b76..f6ab3ccf698f 100644
>>> --- a/scripts/gdb/linux/tasks.py
>>> +++ b/scripts/gdb/linux/tasks.py
>>> @@ -96,6 +96,8 @@ def get_thread_info(task):
>>>          thread_info_addr = task.address + ia64_task_size
>>>          thread_info = thread_info_addr.cast(thread_info_ptr_type)
>>>      else:
>>> +        if task.type.fields()[0].type == thread_info_type.get_type():
>>> +            return task['thread_info']
>>>          thread_info = task['stack'].cast(thread_info_ptr_type)
>>>      return thread_info.dereference()
>>>  
>>>
>>
>> Acked-by: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Andrew, please pick up.
> 
> Acked-by: Kieran Bingham <kbingham@kernel.org>
> 
> However, should we mark this as:
>   Cc: <stable@vger.kernel.org> # 4.9+ ?
> 

Yes, good point.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2018-01-18 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 21:01 Xi Kangjie
2018-01-18 15:43 ` Jan Kiszka
2018-01-18 15:47   ` Kieran Bingham
2018-01-18 15:50     ` Jan Kiszka [this message]

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=273f82e8-7419-a636-c7d3-a0857b478ade@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=akpm@linux-foundation.org \
    --cc=imxikangjie@gmail.com \
    --cc=kbingham@kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®