From: "Thomas Kühnel" <thomas.kuehnel@avm.de>
To: kernel test robot <lkp@intel.com>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: kbuild-all@lists.01.org, ntfs3@lists.linux.dev,
linux-kernel@vger.kernel.org, "Nicolas Schier" <n.schier@avm.de>,
"Thomas Kühnel" <thomas.kuehnel@avm.de>
Subject: Re: [PATCH 1/3] fs/ntfs3: fix endian conversion in ni_fname_name
Date: Thu, 9 Dec 2021 11:50:40 +0100 [thread overview]
Message-ID: <d82ff770-a34c-5ae2-024c-07c4c06c868f@avm.de> (raw)
In-Reply-To: <202112072356.fmLjngs7-lkp@intel.com>
On 07.12.21 17:00, kernel test robot wrote:
> Hi "Thomas,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on 0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1]
>
> url: https://github.com/0day-ci/linux/commits/Thomas-K-hnel/fs-ntfs3-Fixes-for-big-endian-systems/20211207-184206
> base: 0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1
> config: arm64-randconfig-s031-20211207 (https://download.01.org/0day-ci/archive/20211207/202112072356.fmLjngs7-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 11.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.4-dirty
> # https://github.com/0day-ci/linux/commit/d2fb837ced1828c5a57feac3690d3cc8a36b2fdc
> git remote add linux-review https://github.com/0day-ci/linux
> git fetch --no-tags linux-review Thomas-K-hnel/fs-ntfs3-Fixes-for-big-endian-systems/20211207-184206
> git checkout d2fb837ced1828c5a57feac3690d3cc8a36b2fdc
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 SHELL=/bin/bash fs/ntfs3/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
>
> sparse warnings: (new ones prefixed by >>)
>>> fs/ntfs3/frecord.c:1615:28: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted __le16 const [usertype] *s1 @@ got unsigned short const * @@
> fs/ntfs3/frecord.c:1615:28: sparse: expected restricted __le16 const [usertype] *s1
> fs/ntfs3/frecord.c:1615:28: sparse: got unsigned short const *
>
> vim +1615 fs/ntfs3/frecord.c
>
> 1578
> 1579 /* ni_fname_name
> 1580 *
> 1581 * Return: File name attribute by its value.
> 1582 */
> 1583 struct ATTR_FILE_NAME *ni_fname_name(struct ntfs_inode *ni,
> 1584 const struct cpu_str *uni,
Changing the type of uni to struct le_str * should fix the warning.
I'll change this in the next version of this patch.
> 1585 const struct MFT_REF *home_dir,
> 1586 struct mft_inode **mi,
> 1587 struct ATTR_LIST_ENTRY **le)
> 1588 {
> 1589 struct ATTRIB *attr = NULL;
> 1590 struct ATTR_FILE_NAME *fname;
> 1591 struct le_str *fns;
> 1592
> 1593 *le = NULL;
> 1594
> 1595 /* Enumerate all names. */
> 1596 next:
> 1597 attr = ni_find_attr(ni, attr, le, ATTR_NAME, NULL, 0, NULL, mi);
> 1598 if (!attr)
> 1599 return NULL;
> 1600
> 1601 fname = resident_data_ex(attr, SIZEOF_ATTRIBUTE_FILENAME);
> 1602 if (!fname)
> 1603 goto next;
> 1604
> 1605 if (home_dir && memcmp(home_dir, &fname->home, sizeof(*home_dir)))
> 1606 goto next;
> 1607
> 1608 if (!uni)
> 1609 goto next;
> 1610
> 1611 if (uni->len != fname->name_len)
> 1612 goto next;
> 1613
> 1614 fns = (struct le_str *)&fname->name_len;
>> 1615 if (ntfs_cmp_names(uni->name, uni->len, fns->name, fns->len, NULL,
> 1616 false))
> 1617 goto next;
> 1618
> 1619 return fname;
> 1620 }
> 1621
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
next prev parent reply other threads:[~2021-12-09 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 10:24 [PATCH 0/3] fs/ntfs3: Fixes for big endian systems Thomas Kühnel
2021-12-07 10:24 ` [PATCH 1/3] fs/ntfs3: fix endian conversion in ni_fname_name Thomas Kühnel
2021-12-07 16:00 ` kernel test robot
2021-12-09 10:50 ` Thomas Kühnel [this message]
2021-12-07 10:24 ` [PATCH 2/3] fs/ntfs3: add functions to modify LE bitmaps Thomas Kühnel
2021-12-07 17:31 ` kernel test robot
2021-12-07 10:24 ` [PATCH 3/3] fs/ntfs3: use _le variants of bitops functions Thomas Kühnel
2022-12-30 12:07 ` [PATCH 0/3] fs/ntfs3: Fixes for big endian systems Konstantin Komarov
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=d82ff770-a34c-5ae2-024c-07c4c06c868f@avm.de \
--to=thomas.kuehnel@avm.de \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=n.schier@avm.de \
--cc=ntfs3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox