public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: dennisszhou@gmail.com, Dmitry Vyukov <dvyukov@google.com>,
	syzbot <syzbot+adb03f3f0bb57ce3acda@syzkaller.appspotmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	syzkaller-bugs@googlegroups.com
Subject: Re: lost connection to test machine (4)
Date: Mon, 12 Feb 2018 09:03:25 -0800	[thread overview]
Message-ID: <20180212170325.GW695913@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <00c45ca8-305d-1818-e974-a9903c8494b8@iogearbox.net>

Hello, Daniel.

On Mon, Feb 12, 2018 at 06:00:13PM +0100, Daniel Borkmann wrote:
> [ +Dennis, +Tejun ]
> 
> Looks like we're stuck in percpu allocator with key/value size of 4 bytes
> each and large number of entries (max_entries) in the reproducer in above
> link.
> 
> Could we have some __GFP_NORETRY semantics and let allocations fail instead
> of triggering OOM killer?

For some part, maybe, but not generally.  The virt area allocation
goes down to page table allocation which is hard coded to use
GFP_KERNEL in arch mm code.

Thanks.

-- 
tejun

  reply	other threads:[~2018-02-12 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001a113f8734783e94056505f8fd@google.com>
2018-02-12 16:03 ` lost connection to test machine (4) Dmitry Vyukov
2018-02-12 17:00   ` Daniel Borkmann
2018-02-12 17:03     ` Tejun Heo [this message]
2018-02-12 20:05       ` Tejun Heo
2018-02-13 13:35         ` Eric Dumazet
2018-02-13 17:34           ` Dennis Zhou
2018-02-13 17:49             ` Eric Dumazet
2018-02-13 18:13               ` Dennis Zhou
2018-02-14 17:15     ` Dennis Zhou
2018-02-14 17:28       ` syzbot

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=20180212170325.GW695913@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dennisszhou@gmail.com \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+adb03f3f0bb57ce3acda@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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