From: kernel test robot <lkp@intel.com>
To: Prithvi Tambewagh <activprithvi@gmail.com>,
mark@fasheh.com, jlbec@evilplan.org, joseph.qi@linux.alibaba.com
Cc: oe-kbuild-all@lists.linux.dev, ocfs2-devel@lists.linux.dev,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com, khalid@kernel.org,
Prithvi Tambewagh <activprithvi@gmail.com>,
syzbot+c818e5c4559444f88aa0@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] ocfs2: Fix kernel BUG in ocfs2_write_block
Date: Tue, 9 Dec 2025 03:11:32 +0800 [thread overview]
Message-ID: <202512090210.evJEJv5b-lkp@intel.com> (raw)
In-Reply-To: <20251206154819.175479-1-activprithvi@gmail.com>
Hi Prithvi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 24172e0d79900908cf5ebf366600616d29c9b417]
url: https://github.com/intel-lab-lkp/linux/commits/Prithvi-Tambewagh/ocfs2-Fix-kernel-BUG-in-ocfs2_write_block/20251206-235042
base: 24172e0d79900908cf5ebf366600616d29c9b417
patch link: https://lore.kernel.org/r/20251206154819.175479-1-activprithvi%40gmail.com
patch subject: [PATCH] ocfs2: Fix kernel BUG in ocfs2_write_block
config: loongarch-randconfig-r112-20251207 (https://download.01.org/0day-ci/archive/20251209/202512090210.evJEJv5b-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251209/202512090210.evJEJv5b-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/202512090210.evJEJv5b-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/ocfs2/slot_map.c:197:26: sparse: sparse: cast to restricted __le16
>> fs/ocfs2/slot_map.c:197:26: sparse: sparse: cast to restricted __le16
vim +197 fs/ocfs2/slot_map.c
182
183 static int ocfs2_update_disk_slot(struct ocfs2_super *osb,
184 struct ocfs2_slot_info *si,
185 int slot_num)
186 {
187 int status;
188 struct buffer_head *bh;
189
190 spin_lock(&osb->osb_lock);
191 if (si->si_extended)
192 ocfs2_update_disk_slot_extended(si, slot_num, &bh);
193 else
194 ocfs2_update_disk_slot_old(si, slot_num, &bh);
195 spin_unlock(&osb->osb_lock);
196 if (bh->b_blocknr < OCFS2_SUPER_BLOCK_BLKNO) {
> 197 status = ocfs2_error(osb->sb,
198 "Invalid Slot Map Buffer Head "
199 "Block Number : %llu, Should be >= %d",
200 le16_to_cpu(bh->b_blocknr),
201 le16_to_cpu((int)OCFS2_SUPER_BLOCK_BLKNO));
202 if (!status)
203 return -EIO;
204 return status;
205 }
206
207 status = ocfs2_write_block(osb, bh, INODE_CACHE(si->si_inode));
208 if (status < 0)
209 mlog_errno(status);
210
211 return status;
212 }
213
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-12-08 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 15:48 [PATCH] ocfs2: Fix kernel BUG in ocfs2_write_block Prithvi Tambewagh
2025-12-08 19:11 ` 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=202512090210.evJEJv5b-lkp@intel.com \
--to=lkp@intel.com \
--cc=activprithvi@gmail.com \
--cc=david.hunter.linux@gmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=khalid@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+c818e5c4559444f88aa0@syzkaller.appspotmail.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