public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pan Xinhui <xinhui@linux.vnet.ibm.com>
To: Li <kassey1216@gmail.com>, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/hung_task.c: printk address for hung_task
Date: Thu, 14 Jan 2016 10:45:35 +0800	[thread overview]
Message-ID: <56970BCF.2000100@linux.vnet.ibm.com> (raw)
In-Reply-To: <1452652949-7688-1-git-send-email-yingangl@qti.qualcomm.com>

hi, Li
	I have a little confusion. for what you want to know this ptr's value. Can that help you debug or root the cause?
I'm just wondering :)

thanks
xinhui

On 2016年01月13日 10:42, Li wrote:
> From: Kassey Li <kassey1216@gmail.com>
> 
> this is used to check task_struct info when got a dump.
> 
> Signed-off-by: Kassey Li <kassey1216@gmail.com>
> ---
>  kernel/hung_task.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/hung_task.c b/kernel/hung_task.c
> index d234022..b5dd7dd 100644
> --- a/kernel/hung_task.c
> +++ b/kernel/hung_task.c
> @@ -108,8 +108,8 @@ static void check_hung_task(struct task_struct *t, unsigned long timeout)
>  	 * Ok, the task did not get scheduled for more than 2 minutes,
>  	 * complain:
>  	 */
> -	pr_err("INFO: task %s:%d blocked for more than %ld seconds.\n",
> -		t->comm, t->pid, timeout);
> +	pr_err("INFO: task %s:%d 0x%p blocked for more than %ld seconds.\n",
> +		t->comm, t->pid, t, timeout);
>  	pr_err("      %s %s %.*s\n",
>  		print_tainted(), init_utsname()->release,
>  		(int)strcspn(init_utsname()->version, " "),
> 

  reply	other threads:[~2016-01-14  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  2:42 [PATCH] kernel/hung_task.c: printk address for hung_task Li
2016-01-14  2:45 ` Pan Xinhui [this message]
2016-01-14  9:33   ` Kassey
2016-02-17  7:17     ` Kassey

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=56970BCF.2000100@linux.vnet.ibm.com \
    --to=xinhui@linux.vnet.ibm.com \
    --cc=kassey1216@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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