From: Michal Hocko <mhocko@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: Shakeel Butt <shakeelb@google.com>,
kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Greg Thelen <gthelen@google.com>,
Mel Gorman <mgorman@techsingularity.net>,
Vlastimil Babka <vbabka@suse.cz>, Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: save two stranding bit in gfp_mask
Date: Wed, 23 May 2018 10:17:53 +0200 [thread overview]
Message-ID: <20180523081753.GH20441@dhcp22.suse.cz> (raw)
In-Reply-To: <201805231335.RIR9HxYj%fengguang.wu@intel.com>
On Wed 23-05-18 16:08:28, kbuild test robot wrote:
> Hi Shakeel,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on mmotm/master]
> [also build test WARNING on v4.17-rc6]
> [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/Shakeel-Butt/mm-save-two-stranding-bit-in-gfp_mask/20180518-202316
> base: git://git.cmpxchg.org/linux-mmotm.git master
>
What is the warning? Btw. this smells like a failure in the script of
some sort. The patch you are referring doesn't really change any code
except using different valuues for gfp constants which shouldn't make
any difference to any code.
> vim +/jl +2585 fs/reiserfs/journal.c
>
> ^1da177e Linus Torvalds 2005-04-16 2573
> ^1da177e Linus Torvalds 2005-04-16 2574 static struct reiserfs_journal_list *alloc_journal_list(struct super_block *s)
> ^1da177e Linus Torvalds 2005-04-16 2575 {
> ^1da177e Linus Torvalds 2005-04-16 2576 struct reiserfs_journal_list *jl;
> 8c777cc4 Pekka Enberg 2006-02-01 2577 jl = kzalloc(sizeof(struct reiserfs_journal_list),
> 8c777cc4 Pekka Enberg 2006-02-01 2578 GFP_NOFS | __GFP_NOFAIL);
> ^1da177e Linus Torvalds 2005-04-16 2579 INIT_LIST_HEAD(&jl->j_list);
> ^1da177e Linus Torvalds 2005-04-16 2580 INIT_LIST_HEAD(&jl->j_working_list);
> ^1da177e Linus Torvalds 2005-04-16 2581 INIT_LIST_HEAD(&jl->j_tail_bh_list);
> ^1da177e Linus Torvalds 2005-04-16 2582 INIT_LIST_HEAD(&jl->j_bh_list);
> 90415dea Jeff Mahoney 2008-07-25 2583 mutex_init(&jl->j_commit_mutex);
> ^1da177e Linus Torvalds 2005-04-16 2584 SB_JOURNAL(s)->j_num_lists++;
> ^1da177e Linus Torvalds 2005-04-16 @2585 get_journal_list(jl);
> ^1da177e Linus Torvalds 2005-04-16 2586 return jl;
> ^1da177e Linus Torvalds 2005-04-16 2587 }
> ^1da177e Linus Torvalds 2005-04-16 2588
>
> :::::: The code at line 2585 was first introduced by commit
> :::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
>
> :::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
> :::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2018-05-23 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 20:20 [PATCH] mm: save two stranding bit in gfp_mask Shakeel Butt
2018-05-16 20:39 ` Vlastimil Babka
2018-05-16 21:21 ` Shakeel Butt
2018-05-16 20:46 ` Michal Hocko
2018-05-23 8:08 ` kbuild test robot
2018-05-23 8:17 ` Michal Hocko [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=20180523081753.GH20441@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gthelen@google.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mgorman@techsingularity.net \
--cc=shakeelb@google.com \
--cc=vbabka@suse.cz \
/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).