From: Michal Hocko <mhocko@kernel.org>
To: Paul Moore <paul@paul-moore.com>
Cc: mgorman@suse.de,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
selinux@tycho.nsa.gov
Subject: Re: suspicious __GFP_NOMEMALLOC in selinux
Date: Thu, 10 Aug 2017 09:02:06 +0200 [thread overview]
Message-ID: <20170810070206.GA23863@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHC9VhRGmBn7EA1iLzHjv2A3nawc5ZtZs+cjdVm4BUX0wGGHVA@mail.gmail.com>
On Tue 08-08-17 09:34:15, Paul Moore wrote:
> On Mon, Aug 7, 2017 at 2:58 AM, Michal Hocko <mhocko@kernel.org> wrote:
> > On Fri 04-08-17 13:12:04, Paul Moore wrote:
> >> On Fri, Aug 4, 2017 at 3:56 AM, Michal Hocko <mhocko@kernel.org> wrote:
> > [...]
> >> > Btw. Should I resend the patch or somebody will take it from this email
> >> > thread?
> >>
> >> No, unless your mailer mangled the patch I should be able to pull it
> >> from this thread. However, I'm probably going to let this sit until
> >> early next week on the odd chance that anyone else wants to comment on
> >> the flag choice. I'll send another reply once I merge the patch.
> >
> > OK, there is certainly no hurry for merging this. Thanks!
> > --
> > Michal Hocko
> > SUSE Labs
>
> Merged into selinux/next with this patch description, and your
> sign-off (I had to munge the description a bit based on the thread).
> Are you okay with this, especially your sign-off?
Yes. Thanks!
>
> commit 476accbe2f6ef69caeebe99f52a286e12ac35aee
> Author: Michal Hocko <mhocko@kernel.org>
> Date: Thu Aug 3 10:11:52 2017 +0200
>
> selinux: use GFP_NOWAIT in the AVC kmem_caches
>
> There is a strange __GFP_NOMEMALLOC usage pattern in SELinux,
> specifically GFP_ATOMIC | __GFP_NOMEMALLOC which doesn't make much
> sense. GFP_ATOMIC on its own allows to access memory reserves while
> __GFP_NOMEMALLOC dictates we cannot use memory reserves. Replace this
> with the much more sane GFP_NOWAIT in the AVC code as we can tolerate
> memory allocation failures in that code.
>
> Signed-off-by: Michal Hocko <mhocko@kernel.org>
> Acked-by: Mel Gorman <mgorman@suse.de>
> Signed-off-by: Paul Moore <paul@paul-moore.com>
>
> --
> paul moore
> www.paul-moore.com
--
Michal Hocko
SUSE Labs
--
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>
next prev parent reply other threads:[~2017-08-10 7:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 10:50 suspicious __GFP_NOMEMALLOC in selinux Michal Hocko
2017-08-02 21:45 ` Paul Moore
2017-08-03 8:11 ` Michal Hocko
2017-08-03 8:56 ` Mel Gorman
2017-08-03 10:02 ` Tetsuo Handa
2017-08-03 10:33 ` Michal Hocko
2017-08-03 10:44 ` Tetsuo Handa
2017-08-03 11:05 ` Michal Hocko
2017-08-03 18:17 ` Paul Moore
2017-08-04 7:56 ` Michal Hocko
2017-08-04 17:12 ` Paul Moore
2017-08-07 6:58 ` Michal Hocko
2017-08-08 13:34 ` Paul Moore
2017-08-10 7:02 ` Michal Hocko [this message]
2017-08-10 13:49 ` Paul Moore
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=20170810070206.GA23863@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=selinux@tycho.nsa.gov \
/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;
as well as URLs for NNTP newsgroup(s).