From: kernel test robot <lkp@intel.com>
To: Jiaming Zhang <r772577952@gmail.com>,
agruenba@redhat.com, gfs2@lists.linux.dev
Cc: oe-kbuild-all@lists.linux.dev, r772577952@gmail.com,
linux-kernel@vger.kernel.org, syzkaller@googlegroups.com,
stable@vger.kernel.org
Subject: Re: [PATCH] gfs2: validate stuffed inode size before unstuffing
Date: Fri, 14 Aug 2026 03:24:17 +0800 [thread overview]
Message-ID: <202608140317.5gzCSRj5-lkp@intel.com> (raw)
In-Reply-To: <20260705140620.1732914-1-r772577952@gmail.com>
Hi Jiaming,
kernel test robot noticed the following build warnings:
[auto build test WARNING on gfs2/for-next]
[also build test WARNING on linus/master v7.2-rc7 next-20260812]
[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/Jiaming-Zhang/gfs2-validate-stuffed-inode-size-before-unstuffing/20260813-232845
base: https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git for-next
patch link: https://lore.kernel.org/r/20260705140620.1732914-1-r772577952%40gmail.com
patch subject: [PATCH] gfs2: validate stuffed inode size before unstuffing
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20260814/202608140317.5gzCSRj5-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260814/202608140317.5gzCSRj5-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/202608140317.5gzCSRj5-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/gfs2/bmap.c:55 function parameter 'size' not described in 'gfs2_unstuffer_folio'
>> Warning: fs/gfs2/bmap.c:55 function parameter 'size' not described in 'gfs2_unstuffer_folio'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-13 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 13:00 [Linux Kernel Bug] KASAN: out-of-bounds Read in gfs2_unstuff_dinode Jiaming Zhang
2026-07-05 14:06 ` [PATCH] gfs2: validate stuffed inode size before unstuffing Jiaming Zhang
2026-07-06 15:14 ` Andrew Price
2026-07-06 18:00 ` [PATCH v2] gfs2: reject oversized dinode sizes before i_size_write Jiaming Zhang
2026-07-23 7:10 ` Jiaming Zhang
2026-08-06 7:55 ` Jiaming Zhang
2026-08-12 1:36 ` Jiaming Zhang
2026-08-13 19:24 ` kernel test robot [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=202608140317.5gzCSRj5-lkp@intel.com \
--to=lkp@intel.com \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=r772577952@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
/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