linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jitendra Sharma <shajit@codeaurora.org>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Kees Cook <keescook@chromium.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: fs/proc: Crash observed in next_tgid (fs/proc/base.c)
Date: Wed, 17 Apr 2019 22:28:02 +0530	[thread overview]
Message-ID: <e347f9fa-824d-bfe6-055c-1582c42d76e8@codeaurora.org> (raw)
In-Reply-To: <4cb1d095-54a1-a7aa-762f-df77dddc4621@free.fr>

Thanks Marc and Kees for replying.
Answer to your queries:
Kernel version: 4.14.83
Test case: Not some specific test case. Issue reproduced while doing 
monkey testing for very long hours.

Thanks,
Jitendra

On 4/17/2019 5:41 PM, Marc Gonzalez wrote:
> On 15/04/2019 14:58, Jitendra Sharma wrote:
> 
>> We are observing one kernel crash in next_tgid function through
>> getdents64 path. Call stack is as shown below:
> 
> It might help if you specify the exact kernel version you are discussing,
> as in which tag or commit hash you are running.
> 
> Also, what are you doing to trigger the issue?
> 
> Regards.
> 

-- 

QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation

  reply	other threads:[~2019-04-17 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 12:58 fs/proc: Crash observed in next_tgid (fs/proc/base.c) Jitendra Sharma
2019-04-17  3:38 ` Kees Cook
2019-04-17 11:21   ` Oleg Nesterov
2019-04-17 12:11 ` Marc Gonzalez
2019-04-17 16:58   ` Jitendra Sharma [this message]
2019-04-18  9:24     ` Marc Gonzalez
2019-04-17 18:14 Alexey Dobriyan

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=e347f9fa-824d-bfe6-055c-1582c42d76e8@codeaurora.org \
    --to=shajit@codeaurora.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.w.gonzalez@free.fr \
    /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;
as well as URLs for NNTP newsgroup(s).