From: kernel test robot <lkp@intel.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Richard Chang <richardycc@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Brian Geffon <bgeffon@google.com>,
Minchan Kim <minchan@kernel.org>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>
Subject: Re: [PATCH 1/2] zram: introduce compressed data writeback
Date: Sat, 29 Nov 2025 17:07:17 +0800 [thread overview]
Message-ID: <202511291628.NZif1jdx-lkp@intel.com> (raw)
In-Reply-To: <20251128170442.2988502-2-senozhatsky@chromium.org>
Hi Sergey,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on next-20251128]
[cannot apply to axboe/for-next linus/master v6.18-rc7]
[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/Sergey-Senozhatsky/zram-introduce-compressed-data-writeback/20251129-010716
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20251128170442.2988502-2-senozhatsky%40chromium.org
patch subject: [PATCH 1/2] zram: introduce compressed data writeback
config: x86_64-randconfig-011-20251129 (https://download.01.org/0day-ci/archive/20251129/202511291628.NZif1jdx-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251129/202511291628.NZif1jdx-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/202511291628.NZif1jdx-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/block/zram/zram_drv.c:2099:12: warning: 'zram_read_from_zspool_raw' defined but not used [-Wunused-function]
2099 | static int zram_read_from_zspool_raw(struct zram *zram, struct page *page,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/zram_read_from_zspool_raw +2099 drivers/block/zram/zram_drv.c
2098
> 2099 static int zram_read_from_zspool_raw(struct zram *zram, struct page *page,
2100 u32 index)
2101 {
2102 struct zcomp_strm *zstrm;
2103 unsigned long handle;
2104 unsigned int size;
2105 void *src;
2106
2107 handle = zram_get_handle(zram, index);
2108 size = zram_get_obj_size(zram, index);
2109
2110 /*
2111 * We need to get stream just for ->local_copy buffer, in
2112 * case if object spans two physical pages. No decompression
2113 * takes place here, as we read raw compressed data.
2114 */
2115 zstrm = zcomp_stream_get(zram->comps[ZRAM_PRIMARY_COMP]);
2116 src = zs_obj_read_begin(zram->mem_pool, handle, zstrm->local_copy);
2117 memcpy_to_page(page, 0, src, size);
2118 zs_obj_read_end(zram->mem_pool, handle, src);
2119 zcomp_stream_put(zstrm);
2120
2121 return 0;
2122 }
2123
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-29 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 17:04 [PATCH 0/2] " Sergey Senozhatsky
2025-11-28 17:04 ` [PATCH 1/2] " Sergey Senozhatsky
2025-11-29 9:07 ` kernel test robot [this message]
2025-12-01 9:10 ` Sergey Senozhatsky
2025-11-29 9:55 ` Barry Song
2025-12-01 3:56 ` Sergey Senozhatsky
2025-12-01 8:59 ` Barry Song
2025-12-01 9:09 ` Sergey Senozhatsky
2025-12-01 18:00 ` Barry Song
2025-11-28 17:04 ` [PATCH 2/2] zram: rename zram_free_page() Sergey Senozhatsky
2025-12-01 7:39 ` [PATCH 0/2] zram: introduce compressed data writeback Sergey Senozhatsky
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=202511291628.NZif1jdx-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=richardycc@google.com \
--cc=senozhatsky@chromium.org \
/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