From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Hugh Dickins <hughd@google.com>
Subject: Re: 3.15rc2 hanging processes on exit.
Date: Tue, 22 Apr 2014 15:09:28 -0400 [thread overview]
Message-ID: <20140422190928.GA25183@redhat.com> (raw)
In-Reply-To: <CA+55aFxjADAB80AV6qK-b4QPzP7fgog_EyH-7dSpWVgzpZmL8Q@mail.gmail.com>
On Tue, Apr 22, 2014 at 11:57:50AM -0700, Linus Torvalds wrote:
> Are you testing anything new? Or is this strictly new to 3.15? The
> only thing in this area we do differently is commit cda540ace6a1 ("mm:
> get_user_pages(write,force) refuse to COW in shared areas"), but
> fault_in_user_writeable() never used the force bit afaik. Adding Hugh
> just in case.
You mean new as in additions to trinity ?
The only recent chance that might be relevant is that now, when I create
struct iovec's to pass to syscalls, I populate them solely with results
from mmap's rather than a mix of mmaps and mallocs. The mmaps could be
all kinds of sizes, types etc. [*] So now there's more chance I guess
that an iovec contains a bunch of hugepages, or read-only pages etc.
I took another slightly longer trace of what's going on at
http://codemonkey.org.uk/junk/trace2.out
But it looks to me to be pretty similar.
Dave
[*] https://github.com/kernelslacker/trinity/commit/1e73841971717256089d63e9f7fc33972d48028c
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-04-22 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 18:03 3.15rc2 hanging processes on exit Dave Jones
2014-04-22 18:57 ` Linus Torvalds
2014-04-22 19:09 ` Dave Jones [this message]
2014-04-22 20:17 ` Hugh Dickins
2014-04-22 20:32 ` Dave Jones
2014-04-22 20:48 ` Linus Torvalds
2014-04-23 14:49 ` Dave Jones
2014-04-23 15:07 ` Linus Torvalds
2014-04-23 18:11 ` Hugh Dickins
2014-04-23 18:16 ` Dave Jones
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=20140422190928.GA25183@redhat.com \
--to=davej@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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).