All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: kernel test robot <lkp@intel.com>
Cc: <oe-kbuild-all@lists.linux.dev>
Subject: Re: [RFC PATCH] mm: memory-failure: add missing set_mce_nospec() for memory_failure()
Date: Wed, 5 Jul 2023 09:53:48 +0800	[thread overview]
Message-ID: <08b46d38-bf3d-a4b5-b920-797a5fe5aa4a@huawei.com> (raw)
In-Reply-To: <202307050025.piXqvNt6-lkp@intel.com>

On 2023/7/5 0:23, kernel test robot wrote:
> Hi Miaohe,
> 
> [This is a private test report for your RFC patch.]
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on akpm-mm/mm-everything]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Miaohe-Lin/mm-memory-failure-add-missing-set_mce_nospec-for-memory_failure/20230704-202035
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> patch link:    https://lore.kernel.org/r/20230704121948.1331846-1-linmiaohe%40huawei.com
> patch subject: [RFC PATCH] mm: memory-failure: add missing set_mce_nospec() for memory_failure()
> config: arm64-randconfig-r021-20230704 (https://download.01.org/0day-ci/archive/20230705/202307050025.piXqvNt6-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 12.3.0
> reproduce: (https://download.01.org/0day-ci/archive/20230705/202307050025.piXqvNt6-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202307050025.piXqvNt6-lkp@intel.com/

Thanks for reporting. This leads to problem too when I compiled the kernel and it's fixed in my workload but I forgot to post that change to the patch. Sorry for my careless.

	mm/memory-failure.c: In function ‘memory_failure_work_func’:
	mm/memory-failure.c:2412:9: error: suggest parentheses around operand of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’ [-Werror=parentheses]
	 2412 |     if (!entry.flags & MF_SW_SIMULATED)
	      |         ^~~~~~~~~~~~


      reply	other threads:[~2023-07-05  2:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 12:19 [RFC PATCH] mm: memory-failure: add missing set_mce_nospec() for memory_failure() Miaohe Lin
2023-07-04 16:13 ` kernel test robot
2023-07-04 16:23 ` kernel test robot
2023-07-05  1:53   ` Miaohe Lin [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=08b46d38-bf3d-a4b5-b920-797a5fe5aa4a@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.