From: Dave Jones <davej@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: 3.15rc2 hanging processes on exit.
Date: Tue, 22 Apr 2014 16:32:44 -0400 [thread overview]
Message-ID: <20140422203244.GA30757@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1404221303060.6220@eggly.anvils>
On Tue, Apr 22, 2014 at 01:17:33PM -0700, Hugh Dickins wrote:
> Your patch looks to me correct and to the point; but I agree that
> we haven't made a relevant change there recently, so I suppose it
> comes from a trinity improvement rather than a new bug in 3.15.
>
> (Dave, do you have time to confirm that by running new trinity on 3.14?)
I can give it a shot.
I think perhaps a bigger reason why this might be only just turning up,
is that I now have an upper bound on the number of entries in an iovec
at 256 entries. So now there's more chance that we'll generate an iovec
that a syscall can actually use instead of us running out of memory
trying to satisfy every entry and constructing a broken iovec struct if
we hit ENOMEM
Dave
--
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 20:33 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
2014-04-22 20:17 ` Hugh Dickins
2014-04-22 20:32 ` Dave Jones [this message]
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=20140422203244.GA30757@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).