From: kbuild test robot <lkp@intel.com>
To: Nicolas Boichat <drinkcat@chromium.org>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Nicolas Boichat <drinkcat@chromium.org>,
Michal Hocko <mhocko@suse.com>, Joe Perches <joe@perches.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mm@kvack.org, Akinobu Mita <akinobu.mita@gmail.com>,
Pekka Enberg <penberg@kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/failslab: By default, do not fail allocations with direct reclaim only
Date: Tue, 21 May 2019 16:00:10 +0800 [thread overview]
Message-ID: <201905211524.RpQYbGWw%lkp@intel.com> (raw)
In-Reply-To: <20190520044951.248096-1-drinkcat@chromium.org>
Hi Nicolas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.2-rc1 next-20190520]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Nicolas-Boichat/mm-failslab-By-default-do-not-fail-allocations-with-direct-reclaim-only/20190521-045221
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> mm/failslab.c:27:26: sparse: sparse: restricted gfp_t degrades to integer
vim +27 mm/failslab.c
16
17 bool __should_failslab(struct kmem_cache *s, gfp_t gfpflags)
18 {
19 /* No fault-injection for bootstrap cache */
20 if (unlikely(s == kmem_cache))
21 return false;
22
23 if (gfpflags & __GFP_NOFAIL)
24 return false;
25
26 if (failslab.ignore_gfp_reclaim &&
> 27 (gfpflags & ___GFP_DIRECT_RECLAIM))
28 return false;
29
30 if (failslab.cache_filter && !(s->flags & SLAB_FAILSLAB))
31 return false;
32
33 return should_fail(&failslab.attr, s->object_size);
34 }
35
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2019-05-21 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 4:49 Nicolas Boichat
2019-05-20 16:29 ` Akinobu Mita
2019-05-20 17:07 ` David Rientjes
2019-05-20 21:40 ` Nicolas Boichat
2019-05-21 8:00 ` kbuild test robot [this message]
2019-05-21 8:06 ` Nicolas Boichat
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=201905211524.RpQYbGWw%lkp@intel.com \
--to=lkp@intel.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=drinkcat@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=penberg@kernel.org \
--cc=rientjes@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox