public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kohli, Gaurav" <gkohli@codeaurora.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: Query: Crash is coming during /prod/PID/stat and do_exit of same task
Date: Tue, 16 Jan 2018 11:06:47 +0530	[thread overview]
Message-ID: <c43519cb-ce67-96ec-5c55-34b258e47d60@codeaurora.org> (raw)
In-Reply-To: <20180110052017.GB2829@avx2>

On 1/10/2018 10:50 AM, Alexey Dobriyan wrote:

>> We are seeing crash in do_task_stat while accessing stack pointer, It
>> seems same task has already completed do_exit call.
>> So it seems a race between them:
> Please, post exact kernel version and struct task_struct::usage if you
> still have that kernel core (or even full task_struct)

Hi Alexey,

We are working on 4.9.65 and Please find below usage value and other task_struct value,
please let me know if some other data required as well.

crash_64> struct task_struct.usage -x  0xFFFFFFE80D8C2280

   usage = {

     counter = 0x4

   }

struct task_struct.flags -x 0xFFFFFFE80D8C2280

   flags = 0x40870c

crash_64> struct task_struct.exit_code -x 0xFFFFFFE80D8C2280

   exit_code = 0x6

  struct task_struct.state -x 0xFFFFFFE80D8C2280

   state = 0x40
  

Please find below crash stack:

-000|user_stack_pointer(inline)

-000|do_task_stat(

     |    m = 0xFFFFFFE7A5CD7380,

     |    ns = 0xFFFFFF8E7C43C748,

     |  ?,

     |    task = 0xFFFFFFE80D8C2280,

     |  ?)

     |  tty_pgrp = 0

     |  ppid = 2084696064

     |  sid = 0

     |  mm = 0xFFFFFFE7B4424140

     |  tcomm = (84, 9, 71, 122, 142, 255, 255, 255, 48, 253, 240, 165, 231, 255, 255, 255)

     |  flags = 18446743969119403392

-001|proc_tgid_stat(

     |    m = 0xFFFFFFE7A5CD7380,

     |  ?,

     |  ?,

     |  ?)

-002|atomic_sub_return(inline)

Regards
Gaurav

-- 
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

  reply	other threads:[~2018-01-16  5:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10  5:20 Query: Crash is coming during /prod/PID/stat and do_exit of same task Alexey Dobriyan
2018-01-16  5:36 ` Kohli, Gaurav [this message]
2018-01-16  7:20   ` Alexey Dobriyan
2018-01-16  9:44     ` Kohli, Gaurav
  -- strict thread matches above, loose matches on Subject: below --
2018-01-09 13:33 Kohli, Gaurav
2018-01-15 10:04 ` Kohli, Gaurav
2018-01-15 11:02 ` John Ogness
2018-01-15 12:30   ` Kohli, Gaurav

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=c43519cb-ce67-96ec-5c55-34b258e47d60@codeaurora.org \
    --to=gkohli@codeaurora.org \
    --cc=adobriyan@gmail.com \
    --cc=linux-arm-msm@vger.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