From: Michal Hocko <mhocko@kernel.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Mel Gorman <mgorman@suse.de>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: OOM killer invoked during btrfs send/recieve on otherwise idle machine
Date: Fri, 19 Aug 2016 15:27:51 +0200 [thread overview]
Message-ID: <20160819132751.GI32619@dhcp22.suse.cz> (raw)
In-Reply-To: <CAJCQCtQ57OgNgRzjcGr4OBh3y9NO1J0juZbz5p3cgt5OinRx6A@mail.gmail.com>
On Tue 02-08-16 09:48:01, Chris Murphy wrote:
> On Tue, Aug 2, 2016 at 9:38 AM, Chris Murphy <lists@colorremedies.com> wrote:
> > Yesterday I saw oom killer knocking off processes during a simple cp
> > -a from one Btrfs to another, in a VM, with kernel
> > 4.8.0-0.rc0.git3.1.fc25.x86_64. The call trace looks different than
> > Markus' so I'm not sure it's the same problem. It's not always
> > reproducible. It hasn't happened on 4.7.0 though. According ot koji
> > this is Linux v4.7-6438-gc624c86
> >
> > This is 'journalctl -o short-monotonic -b-4 -k'
> >
> > https://drive.google.com/open?id=0B_2Asp8DGjJ9ZC1JSDJnaWpnSEE
>
> Btrfs volume 2 is created at [ 625.769736] and mounted at [
> 640.119150], with the copy starting shortly after that. OOM happens at
> [ 856.212658] . There are a bunch of earlier bug messages, BUG:
> sleeping function called from invalid context at mm/slab.h:393.
It seems that the current linux-next +
http://lkml.kernel.org/r/f7a9ea9d-bb88-bfd6-e340-3a933559305a@suse.cz
seems like helped other users. Could you try this as well please?
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2016-08-19 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 5:11 Markus Trippelsdorf
2016-07-31 15:10 ` Michal Hocko
2016-07-31 15:25 ` Markus Trippelsdorf
2016-08-02 13:28 ` Michal Hocko
2016-08-02 15:38 ` Chris Murphy
2016-08-02 15:48 ` Chris Murphy
2016-08-19 13:27 ` Michal Hocko [this message]
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=20160819132751.GI32619@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=mgorman@suse.de \
/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
all inboxes | Powered by JetHome®