public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mel Gorman <mgorman@suse.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: [mel:mm-reclaimcongest-v1r4 1/5] mm/vmscan.c:1015:7: error: variable 'ret' set but not used
Date: Thu, 30 Sep 2021 08:41:28 +0800	[thread overview]
Message-ID: <202109300822.FAHExXbk-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git mm-reclaimcongest-v1r4
head:   07285068a0f1fb7bee052bf5a4b71c4d8d4b2f77
commit: a7f2d5fd13a3022b3906b6f849998b726fa3eb83 [1/5] mm/vmscan: Throttle reclaim until some writeback completes if congested
config: hexagon-buildonly-randconfig-r005-20210929 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project dc6e8dfdfe7efecfda318d43a06fae18b40eb498)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git/commit/?id=a7f2d5fd13a3022b3906b6f849998b726fa3eb83
        git remote add mel https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git
        git fetch --no-tags mel mm-reclaimcongest-v1r4
        git checkout a7f2d5fd13a3022b3906b6f849998b726fa3eb83
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=hexagon 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> mm/vmscan.c:1015:7: error: variable 'ret' set but not used [-Werror,-Wunused-but-set-variable]
           long ret;
                ^
   mm/vmscan.c:1381:6: error: variable 'err' set but not used [-Werror,-Wunused-but-set-variable]
           int err;
               ^
   2 errors generated.


vim +/ret +1015 mm/vmscan.c

  1008	
  1009	static void
  1010	reclaim_throttle(pg_data_t *pgdat, enum vmscan_throttle_state reason,
  1011								long timeout)
  1012	{
  1013		wait_queue_head_t *wqh = &pgdat->reclaim_wait;
  1014		unsigned long start = jiffies;
> 1015		long ret;
  1016		DEFINE_WAIT(wait);
  1017	
  1018		atomic_inc(&pgdat->nr_reclaim_throttled);
  1019		WRITE_ONCE(pgdat->nr_reclaim_start,
  1020			 node_page_state(pgdat, NR_THROTTLED_WRITTEN));
  1021	
  1022		prepare_to_wait(wqh, &wait, TASK_INTERRUPTIBLE);
  1023		ret = schedule_timeout(timeout);
  1024		finish_wait(wqh, &wait);
  1025		atomic_dec(&pgdat->nr_reclaim_throttled);
  1026	
  1027		trace_mm_vmscan_throttled(pgdat->node_id, jiffies_to_usecs(timeout),
  1028					jiffies_to_usecs(jiffies - start),
  1029					reason);
  1030	}
  1031	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28929 bytes --]

                 reply	other threads:[~2021-09-30  0:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202109300822.FAHExXbk-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mgorman@suse.de \
    /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