From: Paul Moore <paul@paul-moore.com>
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
Subject: Re: [PATCH] selinux: use __GFP_NOWARN with GFP_NOWAIT
Date: Thu, 10 Jun 2021 21:15:17 -0400 [thread overview]
Message-ID: <CAHC9VhStg=5soOqXMJUoik_A9N1PLABMbU8pZZcZ8=k=_U_JxA@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhTYeOmJqoyEniXLGMv3cJGBW4_BLc3LhDLBDhQCKtfp7Q@mail.gmail.com>
On Thu, Jun 10, 2021 at 7:13 PM Paul Moore <paul@paul-moore.com> wrote:
> 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.
Looks fine to me, merged into selinux/next - thanks!
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2021-06-11 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 16:37 [PATCH] selinux: use __GFP_NOWARN with GFP_NOWAIT Minchan Kim
2021-06-10 23:06 ` Andrew Morton
2021-06-10 23:13 ` Paul Moore
2021-06-11 1:15 ` Paul Moore [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='CAHC9VhStg=5soOqXMJUoik_A9N1PLABMbU8pZZcZ8=k=_U_JxA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=akpm@linux-foundation.org \
--cc=joaodias@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=selinux@vger.kernel.org \
--cc=surenb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.