linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ryusuke Konishi <konishi.ryusuke@gmail.com>,
	Hugh Dickins <hughd@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Yosry Ahmed <yosry.ahmed@linux.dev>,
	Nhat Pham <nphamcs@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Matthew Wilcox <willy@infradead.org>,
	Chengming Zhou <chengming.zhou@linux.dev>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	linux-nilfs@vger.kernel.org
Subject: Re: [PATCH 5/7] mm: stop passing a writeback_control structure to swap_writeout
Date: Thu, 8 May 2025 19:38:56 +0800	[thread overview]
Message-ID: <202505081941.kyY28sRZ-lkp@intel.com> (raw)
In-Reply-To: <20250508054938.15894-6-hch@lst.de>

Hi Christoph,

kernel test robot noticed the following build errors:

[auto build test ERROR on next-20250507]
[cannot apply to akpm-mm/mm-everything konis-nilfs2/upstream linus/master v6.15-rc5 v6.15-rc4 v6.15-rc3 v6.15-rc5]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Christoph-Hellwig/mm-stop-passing-a-writeback_control-structure-to-shmem_writeout/20250508-144804
base:   next-20250507
patch link:    https://lore.kernel.org/r/20250508054938.15894-6-hch%40lst.de
patch subject: [PATCH 5/7] mm: stop passing a writeback_control structure to swap_writeout
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20250508/202505081941.kyY28sRZ-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250508/202505081941.kyY28sRZ-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/202505081941.kyY28sRZ-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/vmscan.c: In function 'writeout':
>> mm/vmscan.c:670:44: error: passing argument 2 of 'swap_writeout' from incompatible pointer type [-Wincompatible-pointer-types]
     670 |                 res = swap_writeout(folio, plug);
         |                                            ^~~~
         |                                            |
         |                                            struct swap_iocb **
   In file included from mm/vmscan.c:69:
   mm/swap.h:146:76: note: expected 'struct writeback_control *' but argument is of type 'struct swap_iocb **'
     146 | static inline int swap_writeout(struct folio *f, struct writeback_control *wbc)
         |                                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
--
   mm/shmem.c: In function 'shmem_writeout':
>> mm/shmem.c:1644:45: error: passing argument 2 of 'swap_writeout' from incompatible pointer type [-Wincompatible-pointer-types]
    1644 |                 return swap_writeout(folio, plug);
         |                                             ^~~~
         |                                             |
         |                                             struct swap_iocb **
   In file included from mm/shmem.c:44:
   mm/swap.h:146:76: note: expected 'struct writeback_control *' but argument is of type 'struct swap_iocb **'
     146 | static inline int swap_writeout(struct folio *f, struct writeback_control *wbc)
         |                                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~


vim +/swap_writeout +670 mm/vmscan.c

   654	
   655	static pageout_t writeout(struct folio *folio, struct address_space *mapping,
   656			struct swap_iocb **plug, struct list_head *folio_list)
   657	{
   658		int res;
   659	
   660		folio_set_reclaim(folio);
   661	
   662		/*
   663		 * The large shmem folio can be split if CONFIG_THP_SWAP is not enabled
   664		 * or we failed to allocate contiguous swap entries, in which case
   665		 * the split out folios get added back to folio_list.
   666		 */
   667		if (shmem_mapping(mapping))
   668			res = shmem_writeout(folio, plug, folio_list);
   669		else
 > 670			res = swap_writeout(folio, plug);
   671	
   672		if (res < 0)
   673			handle_write_error(mapping, folio, res);
   674		if (res == AOP_WRITEPAGE_ACTIVATE) {
   675			folio_clear_reclaim(folio);
   676			return PAGE_ACTIVATE;
   677		}
   678	
   679		/* synchronous write? */
   680		if (!folio_test_writeback(folio))
   681			folio_clear_reclaim(folio);
   682	
   683		trace_mm_vmscan_write_folio(folio);
   684		node_stat_add_folio(folio, NR_VMSCAN_WRITE);
   685		return PAGE_SUCCESS;
   686	}
   687	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


  reply	other threads:[~2025-05-08 11:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  5:47 stop passing a writeback_control to swap/shmem writeout Christoph Hellwig
2025-05-08  5:47 ` [PATCH 1/7] mm: split out a writeout helper from pageout Christoph Hellwig
2025-05-08  5:47 ` [PATCH 2/7] mm: stop passing a writeback_control structure to shmem_writeout Christoph Hellwig
2025-05-08 13:03   ` kernel test robot
2025-05-08 13:25   ` Matthew Wilcox
2025-05-08 14:03     ` Christoph Hellwig
2025-05-08  5:47 ` [PATCH 3/7] mm: tidy up swap_writeout Christoph Hellwig
2025-05-08  5:47 ` [PATCH 4/7] mm: stop passing a writeback_control structure to __swap_writepage Christoph Hellwig
2025-05-08  5:47 ` [PATCH 5/7] mm: stop passing a writeback_control structure to swap_writeout Christoph Hellwig
2025-05-08 11:38   ` kernel test robot [this message]
2025-05-08  5:47 ` [PATCH 6/7] nilfs2: remove wbc->for_reclaim handling Christoph Hellwig
2025-05-08 16:16   ` Ryusuke Konishi
2025-05-16  4:55     ` Christoph Hellwig
2025-05-16  6:08       ` Ryusuke Konishi
2025-05-08  5:47 ` [PATCH 7/7] mm: remove the for_reclaim field from struct writeback_control Christoph Hellwig

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=202505081941.kyY28sRZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=chengming.zhou@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=hch@lst.de \
    --cc=hughd@google.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=nphamcs@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=willy@infradead.org \
    --cc=yosry.ahmed@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox