linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: davem@davemloft.net, netfilter-devel@vger.kernel.org,
	coreteam@netfilter.org, netdev@vger.kernel.org,
	aarcange@redhat.com, yang.s@alibaba-inc.com, mhocko@suse.com,
	syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
	mingo@kernel.org, linux-mm@kvack.org, rientjes@google.com,
	akpm@linux-foundation.org, guro@fb.com,
	kirill.shutemov@linux.intel.com
Subject: Re: [netfilter-core] kernel panic: Out of memory and no killable processes... (2)
Date: Mon, 29 Jan 2018 08:23:57 +0100	[thread overview]
Message-ID: <20180129072357.GD5906@breakpoint.cc> (raw)
In-Reply-To: <201801290020.w0T0KK8V015938@www262.sakura.ne.jp>

Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote:
> syzbot wrote:
> > syzbot hit the following crash on net-next commit
> > 6bb46bc57c8e9ce947cc605e555b7204b44d2b10 (Fri Jan 26 16:00:23 2018 +0000)
> > Merge branch 'cxgb4-fix-dump-collection-when-firmware-crashed'
> > 
> > C reproducer is attached.
> > syzkaller reproducer is attached.
> > Raw console output is attached.
> > compiler: gcc (GCC) 7.1.1 20170620
> > .config is attached.
> > 
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+8630e35fc7287b392aac@syzkaller.appspotmail.com
> > It will help syzbot understand when the bug is fixed. See footer for  
> > details.
> > If you forward the report, please keep this part and the footer.
> > 
> > [ 3685]     0  3685    17821        1   184320        0             0 sshd
> > [ 3692]     0  3692     4376        0    32768        0             0  
> > syzkaller025682
> > [ 3695]     0  3695     4376        0    36864        0             0  
> > syzkaller025682
> > Kernel panic - not syncing: Out of memory and no killable processes...
> > 
> 
> This sounds like too huge vmalloc() request where size is controlled by userspace.

Right.

Before eacd86ca3b036e55e172b7279f101cef4a6ff3a4
this used 

              info = __vmalloc(sz, GFP_KERNEL | __GFP_NOWARN | __GFP_NORETRY,

would it help to re-add that?

> vmalloc() once became killable by commit 5d17a73a2ebeb8d1 ("vmalloc: back
> off when the current task is killed") but then became unkillable by commit
> b8c8a338f75e052d ("Revert "vmalloc: back off when the current task is
> killed""). Therefore, we can't handle this problem from MM side.
> Please consider adding some limit from networking side.

I don't know what "some limit" would be.  I would prefer if there was
a way to supress OOM Killer in first place so we can just -ENOMEM user.

AFAIU NOWARN|NORETRY does that, so I would propose to just read-add it?

--
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>

  reply	other threads:[~2018-01-29  7:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28 17:58 syzbot
2018-01-29  0:20 ` Tetsuo Handa
2018-01-29  7:23   ` Florian Westphal [this message]
2018-01-29  8:26     ` [netfilter-core] " Kirill A. Shutemov
2018-01-29 16:57       ` Florian Westphal
2018-01-29 18:24         ` Jan Engelhardt
2018-01-29 18:25         ` Michal Hocko
2018-01-29 18:28         ` Kirill A. Shutemov
2018-01-29 22:35           ` Florian Westphal
2018-01-30  7:52             ` Michal Hocko
2018-01-30  8:11               ` Florian Westphal
2018-01-30  8:28                 ` Kirill A. Shutemov
2018-01-30  9:02                   ` Dmitry Vyukov
2018-01-30  9:57                     ` Michal Hocko
2018-01-30 14:01                       ` Michal Hocko
2018-01-30 14:01                         ` Florian Westphal
2018-01-30 14:39                           ` Michal Hocko
2018-02-02 11:41                             ` Pablo Neira Ayuso
2018-01-30 19:27                         ` Andrew Morton
2018-01-31  8:19                           ` Michal Hocko
2018-02-07 17:44                             ` Pablo Neira Ayuso
2018-02-07 19:06                               ` Andrew Morton
2018-02-07 19:15                                 ` Pablo Neira Ayuso
2018-01-30  9:51                 ` Michal Hocko
2018-03-23 10:40 ` Tetsuo Handa
2018-03-23 11:23   ` 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=20180129072357.GD5906@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=guro@fb.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=rientjes@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yang.s@alibaba-inc.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