Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210609163717.2719253-1-minchan@kernel.org> <20210610160650.d2112a9db8130224c597bfaf@linux-foundation.org>
In-Reply-To: <20210610160650.d2112a9db8130224c597bfaf@linux-foundation.org>
From:   Paul Moore <paul@paul-moore.com>
Date:   Thu, 10 Jun 2021 19:13:16 -0400
Message-ID: <CAHC9VhTYeOmJqoyEniXLGMv3cJGBW4_BLc3LhDLBDhQCKtfp7Q@mail.gmail.com>
Subject: Re: [PATCH] selinux: use __GFP_NOWARN with GFP_NOWAIT
To:     Andrew Morton <akpm@linux-foundation.org>
Cc:     Minchan Kim <minchan@kernel.org>, Michal Hocko <mhocko@suse.com>,
        linux-mm <linux-mm@kvack.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Suren Baghdasaryan <surenb@google.com>,
        John Dias <joaodias@google.com>, selinux@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Jun 10, 2021 at 7:06 PM Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed,  9 Jun 2021 09:37:17 -0700 Minchan Kim <minchan@kernel.org> wrote:
>
> > In the field, we have seen lots of allocation failure from the call path below.
> >
> > ...
> >
> > Based on [1], selinux is tolerate for failure of memory allocation.
> > Then, use __GFP_NOWARN together.
> >
>
> Thanks.  I trust that the selinux developers will process this patch.

That's the plan; this is in my review queue for this evening.

-- 
paul moore
www.paul-moore.com