linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Jitendra Sharma <shajit@codeaurora.org>
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 14:11:45 +0200	[thread overview]
Message-ID: <4cb1d095-54a1-a7aa-762f-df77dddc4621@free.fr> (raw)
In-Reply-To: <b5b9df7b-324c-8286-3a7c-e7812511772d@codeaurora.org>

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.

  parent reply	other threads:[~2019-04-17 12:11 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 [this message]
2019-04-17 16:58   ` Jitendra Sharma
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=4cb1d095-54a1-a7aa-762f-df77dddc4621@free.fr \
    --to=marc.w.gonzalez@free.fr \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shajit@codeaurora.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;
as well as URLs for NNTP newsgroup(s).