lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 5 Apr 2018 10:30:50 -0400
From:   Steven Rostedt <>
To:     Matthew Wilcox <>
Cc:     Joel Fernandes <>,
        Michal Hocko <>,
        Zhaoyang Huang <>,
        Ingo Molnar <>,
        LKML <>,,
        Andrew Morton <>,
        "open list:MEMORY MANAGEMENT" <>,
        Vlastimil Babka <>
Subject: Re: [PATCH v1] kernel/trace:check the val against the available mem

On Thu, 5 Apr 2018 07:22:58 -0700
Matthew Wilcox <> wrote:

> I understand you don't want GFP_NORETRY.  But why is it more important for
> this allocation to succeed than other normal GFP_KERNEL allocations?

Not sure what you mean by "more important"? Does saying "RETRY_MAYFAIL"
make it more important? The difference is, if GFP_KERNEL fails, we
don't want to trigger an OOM, and simply clean up and report -ENOMEM to
the user. It has nothing to do with being more important than other

If there's 100 Megs of memory available, and the user requests a gig of
memory, it's going to fail. Ideally, it doesn't trigger OOM, but
instead simply reports -ENOMEM to the user.

-- Steve

Powered by blists - more mailing lists