All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android11-5.4 7243/28637] fs/incfs/data_mgmt.h:318:44: sparse: sparse: cast truncates bits from constant value (5346434e49 becomes 46434e49)
Date: Thu, 14 Dec 2023 03:37:59 +0800	[thread overview]
Message-ID: <202312140303.bJY8d8Wo-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android11-5.4
head:   f51804072bcc58759ff6228a3d73edadfb5cf787
commit: 6a5003146f8798ddd9f3f912c516208af7106a1b [7243/28637] ANDROID: Incremental fs: Fix four error-path bugs
config: i386-randconfig-061-20231110 (https://download.01.org/0day-ci/archive/20231214/202312140303.bJY8d8Wo-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231214/202312140303.bJY8d8Wo-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/202312140303.bJY8d8Wo-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   fs/incfs/data_mgmt.c: note: in included file:
>> fs/incfs/data_mgmt.h:318:44: sparse: sparse: cast truncates bits from constant value (5346434e49 becomes 46434e49)
--
   fs/incfs/vfs.c: note: in included file:
>> fs/incfs/data_mgmt.h:318:44: sparse: sparse: cast truncates bits from constant value (5346434e49 becomes 46434e49)
   fs/incfs/vfs.c:1257:48: sparse: sparse: non size-preserving integer to pointer cast
   fs/incfs/vfs.c:2181:23: sparse: sparse: cast truncates bits from constant value (5346434e49 becomes 46434e49)

vim +318 fs/incfs/data_mgmt.h

   295	
   296	/*
   297	 * Collects pending reads and saves them into the array (reads/reads_size).
   298	 * Only reads with serial_number > sn_lowerbound are reported.
   299	 * Returns how many reads were saved into the array.
   300	 */
   301	int incfs_collect_pending_reads(struct mount_info *mi, int sn_lowerbound,
   302					struct incfs_pending_read_info *reads,
   303					int reads_size);
   304	
   305	int incfs_collect_logged_reads(struct mount_info *mi,
   306				       struct read_log_state *start_state,
   307				       struct incfs_pending_read_info *reads,
   308				       int reads_size);
   309	struct read_log_state incfs_get_log_state(struct mount_info *mi);
   310	int incfs_get_uncollected_logs_count(struct mount_info *mi,
   311					     const struct read_log_state *state);
   312	
   313	static inline struct inode_info *get_incfs_node(struct inode *inode)
   314	{
   315		if (!inode)
   316			return NULL;
   317	
 > 318		if (inode->i_sb->s_magic != (long) INCFS_MAGIC_NUMBER) {
   319			/* This inode doesn't belong to us. */
   320			pr_warn_once("incfs: %s on an alien inode.", __func__);
   321			return NULL;
   322		}
   323	
   324		return container_of(inode, struct inode_info, n_vfs_inode);
   325	}
   326	

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

                 reply	other threads:[~2023-12-13 19:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202312140303.bJY8d8Wo-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --cc=oe-kbuild-all@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.