mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ethan Ferguson <ethan.ferguson@zetier.com>,
	linkinjeon@kernel.org, sj1557.seo@samsung.com
Cc: oe-kbuild-all@lists.linux.dev, yuezhang.mo@sony.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ethan Ferguson <ethan.ferguson@zetier.com>
Subject: Re: [PATCH 1/1] exfat: Add support for FS_IOC_{GET,SET}FSLABEL
Date: Sat, 16 Aug 2025 20:38:24 +0800	[thread overview]
Message-ID: <202508162026.aFXpZAKm-lkp@intel.com> (raw)
In-Reply-To: <20250815171056.103751-2-ethan.ferguson@zetier.com>

Hi Ethan,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 37816488247ddddbc3de113c78c83572274b1e2e]

url:    https://github.com/intel-lab-lkp/linux/commits/Ethan-Ferguson/exfat-Add-support-for-FS_IOC_-GET-SET-FSLABEL/20250816-011428
base:   37816488247ddddbc3de113c78c83572274b1e2e
patch link:    https://lore.kernel.org/r/20250815171056.103751-2-ethan.ferguson%40zetier.com
patch subject: [PATCH 1/1] exfat: Add support for FS_IOC_{GET,SET}FSLABEL
config: nios2-randconfig-r121-20250816 (https://download.01.org/0day-ci/archive/20250816/202508162026.aFXpZAKm-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250816/202508162026.aFXpZAKm-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/202508162026.aFXpZAKm-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/exfat/super.c:656:28: sparse: sparse: incorrect type in argument 1 (different base types) @@     expected unsigned short const [usertype] *ucs1 @@     got restricted __le16 * @@
   fs/exfat/super.c:656:28: sparse:     expected unsigned short const [usertype] *ucs1
   fs/exfat/super.c:656:28: sparse:     got restricted __le16 *

vim +656 fs/exfat/super.c

   639	
   640	int exfat_write_volume_label(struct super_block *sb)
   641	{
   642		int ret;
   643		struct exfat_sb_info *sbi = EXFAT_SB(sb);
   644		struct buffer_head *bh;
   645		struct exfat_dentry *ep;
   646	
   647		ret = exfat_get_volume_label_ptrs(sb, &bh, &ep);
   648		if (ret < 0)
   649			goto cleanup;
   650	
   651		mutex_lock(&sbi->s_lock);
   652		memcpy(ep->dentry.volume_label.volume_label, sbi->volume_label,
   653					sizeof(sbi->volume_label));
   654	
   655		ep->dentry.volume_label.char_count =
 > 656			UniStrnlen(ep->dentry.volume_label.volume_label,
   657					EXFAT_VOLUME_LABEL_LEN);
   658		mutex_unlock(&sbi->s_lock);
   659	
   660	cleanup:
   661		if (bh) {
   662			exfat_update_bh(bh, true);
   663			brelse(bh);
   664		}
   665	
   666		return ret;
   667	}
   668	

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

      reply	other threads:[~2025-08-16 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 17:10 [PATCH 0/1] " Ethan Ferguson
2025-08-15 17:10 ` [PATCH 1/1] " Ethan Ferguson
2025-08-16 12:38   ` 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=202508162026.aFXpZAKm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ethan.ferguson@zetier.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sj1557.seo@samsung.com \
    --cc=yuezhang.mo@sony.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

all inboxes | Powered by JetHome®