From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933022AbeARPz0 (ORCPT ); Thu, 18 Jan 2018 10:55:26 -0500 Received: from mail.kernel.org ([198.145.29.99]:49182 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932668AbeARPy6 (ORCPT ); Thu, 18 Jan 2018 10:54:58 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 91E3F21742 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=kbingham@kernel.org Subject: Re: [PATCH] scripts/gdb: fix get_thread_info To: Jan Kiszka , Xi Kangjie , Andrew Morton Cc: linux-kernel@vger.kernel.org References: <20180118210159.17223-1-imxikangjie@gmail.com> From: Kieran Bingham Message-ID: <782503b9-83fc-6a47-24ba-524a728da642@kernel.org> Date: Thu, 18 Jan 2018 15:47:31 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 >> --- >> 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 > > Andrew, please pick up. Acked-by: Kieran Bingham However, should we mark this as: Cc: # 4.9+ ? Regards -- Kieran