From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Hocko <mhocko@suse.cz>,
Ralf-Peter Rohbeck <Ralf-Peter.Rohbeck@quantum.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Oleg Nesterov <oleg@redhat.com>,
Vladimir Davydov <vdavydov@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
Jiri Slaby <jslaby@suse.com>, Olaf Hering <olaf@aepfle.de>,
Joonsoo Kim <js1304@gmail.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: More OOM problems
Date: Tue, 11 Oct 2016 09:10:13 +0200 [thread overview]
Message-ID: <c71036ae-73db-f05a-fd14-fe2de44515b9@suse.cz> (raw)
In-Reply-To: <20161011064426.GA31996@dhcp22.suse.cz>
On 10/11/2016 08:44 AM, Michal Hocko wrote:
> [Let's restore the CC list]
>
> On Mon 10-10-16 10:20:27, Ralf-Peter Rohbeck wrote:
>> I ran my torture test overnight (after finding the last linux-next branch
>> that compiled, sigh...):
>> Wrote two 4TB USB3 drives, compiled a kernel and ran my btrfs dedup script
>> in parallel.
>
> Thanks for testing and good to hear that premature OOMs are gone
Great indeed. Note that meanwhile the patches went to mainline so we'd
definitely welcome testing from the rest of you who had originally problems with
4.7/4.8 and didn't try the linux-next recently. So a good point would be to test
4.9-rc1 when it's released. I hope you don't want to discover regressions again
too late, in the 4.9 final release :)
Vlastimil
--
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:[~2016-10-11 7:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eafb59b5-0a2b-0e28-ca79-f044470a2851@Quantum.com>
[not found] ` <20160930214448.GB28379@dhcp22.suse.cz>
[not found] ` <982671bd-5733-0cd5-c15d-112648ff14c5@Quantum.com>
2016-10-11 6:44 ` More OOM problems Michal Hocko
2016-10-11 7:10 ` Vlastimil Babka [this message]
2016-10-30 4:17 ` Simon Kirby
2016-10-31 21:41 ` Vlastimil Babka
2016-10-31 21:51 ` Vlastimil Babka
2016-09-18 20:03 Linus Torvalds
2016-09-18 20:26 ` Lorenzo Stoakes
2016-09-18 20:58 ` Linus Torvalds
2016-09-18 21:13 ` Vlastimil Babka
2016-09-18 21:34 ` Lorenzo Stoakes
2016-09-19 8:32 ` Michal Hocko
2016-09-19 8:42 ` Lorenzo Stoakes
2016-09-19 8:53 ` Michal Hocko
2016-09-25 21:48 ` Lorenzo Stoakes
2016-09-26 7:48 ` Michal Hocko
2016-09-18 21:00 ` Vlastimil Babka
2016-09-18 21:18 ` Linus Torvalds
2016-09-19 6:27 ` Jiri Slaby
2016-09-19 7:01 ` Michal Hocko
2016-09-19 7:52 ` Michal Hocko
2016-09-19 1:07 ` Andi Kleen
[not found] ` <alpine.DEB.2.20.1609190836540.12121@east.gentwo.org>
2016-09-19 14:31 ` Andi Kleen
2016-09-19 14:39 ` Michal Hocko
2016-09-19 14:41 ` Vlastimil Babka
2016-09-19 18:18 ` Linus Torvalds
2016-09-19 19:57 ` Christoph Lameter
2016-09-18 22:00 ` Vlastimil Babka
2016-09-19 6:56 ` Michal Hocko
2016-09-19 6:48 ` Michal Hocko
2016-09-21 7:04 ` Raymond Jennings
2016-09-21 7:29 ` Michal Hocko
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=c71036ae-73db-f05a-fd14-fe2de44515b9@suse.cz \
--to=vbabka@suse.cz \
--cc=Ralf-Peter.Rohbeck@quantum.com \
--cc=a.miskiewicz@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=js1304@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-mm@kvack.org \
--cc=markus@trippelsdorf.de \
--cc=mhocko@suse.cz \
--cc=olaf@aepfle.de \
--cc=oleg@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=torvalds@linux-foundation.org \
--cc=vdavydov@parallels.com \
/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).