From: Alexey Dobriyan <adobriyan@gmail.com>
To: shajit@codeaurora.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: fs/proc: Crash observed in next_tgid (fs/proc/base.c)
Date: Wed, 17 Apr 2019 21:14:55 +0300 [thread overview]
Message-ID: <20190417181455.GA2965@avx2> (raw)
> Test case: Not some specific test case.
Write 2 programs: one forks, clones, and execs randomly (but not going
out of control), another does open("/proc"), getdents in a loop.
Don't use shell scripts or readdir as they only bring overhead.
Run getdents in a loop and several forkers, see what happens.
next reply other threads:[~2019-04-17 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 18:14 Alexey Dobriyan [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2019-04-18 9:24 ` Marc Gonzalez
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=20190417181455.GA2965@avx2 \
--to=adobriyan@gmail.com \
--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).