From: kernel test robot <lkp@intel.com> To: Gabriel Krisman Bertazi <krisman@collabora.com>, tytso@mit.edu, adilger.kernel@dilger.ca, jaegeuk@kernel.org Cc: kbuild-all@lists.01.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, ebiggers@kernel.org, Gabriel Krisman Bertazi <krisman@collabora.com>, kernel@collabora.com Subject: Re: [PATCH v3 1/7] ext4: Match the f2fs ci_compare implementation Date: Tue, 10 May 2022 02:08:20 +0800 [thread overview] Message-ID: <202205100125.ebeEi8X2-lkp@intel.com> (raw) In-Reply-To: <20220429182728.14008-2-krisman@collabora.com> Hi Gabriel, I love your patch! Perhaps something to improve: [auto build test WARNING on tytso-ext4/dev] [also build test WARNING on jaegeuk-f2fs/dev-test linus/master v5.18-rc6 next-20220509] [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] url: https://github.com/intel-lab-lkp/linux/commits/Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220430-022957 base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev config: x86_64-rhel-8.3-func (https://download.01.org/0day-ci/archive/20220510/202205100125.ebeEi8X2-lkp@intel.com/config) compiler: gcc-11 (Debian 11.2.0-20) 11.2.0 reproduce (this is a W=1 build): # https://github.com/intel-lab-lkp/linux/commit/6bf2e9e6750865e9e033adc185eacd37e8b5b0dd git remote add linux-review https://github.com/intel-lab-lkp/linux git fetch --no-tags linux-review Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220430-022957 git checkout 6bf2e9e6750865e9e033adc185eacd37e8b5b0dd # save the config file mkdir build_dir && cp config build_dir/.config make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/ext4/ fs/f2fs/ If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> All warnings (new ones prefixed by >>): fs/ext4/namei.c: In function 'ext4_match': >> fs/ext4/namei.c:1430:13: warning: unused variable 'ret' [-Wunused-variable] 1430 | int ret; | ^~~ vim +/ret +1430 fs/ext4/namei.c 1419 1420 /* 1421 * Test whether a directory entry matches the filename being searched for. 1422 * 1423 * Return: %true if the directory entry matches, otherwise %false. 1424 */ 1425 static bool ext4_match(struct inode *parent, 1426 const struct ext4_filename *fname, 1427 struct ext4_dir_entry_2 *de) 1428 { 1429 struct fscrypt_name f; > 1430 int ret; 1431 1432 if (!de->inode) 1433 return false; 1434 1435 f.usr_fname = fname->usr_fname; 1436 f.disk_name = fname->disk_name; 1437 #ifdef CONFIG_FS_ENCRYPTION 1438 f.crypto_buf = fname->crypto_buf; 1439 #endif 1440 -- 0-DAY CI Kernel Test Service https://01.org/lkp
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com> To: Gabriel Krisman Bertazi <krisman@collabora.com>, tytso@mit.edu, adilger.kernel@dilger.ca, jaegeuk@kernel.org Cc: kernel@collabora.com, kbuild-all@lists.01.org, linux-f2fs-devel@lists.sourceforge.net, ebiggers@kernel.org, linux-ext4@vger.kernel.org, Gabriel Krisman Bertazi <krisman@collabora.com> Subject: Re: [f2fs-dev] [PATCH v3 1/7] ext4: Match the f2fs ci_compare implementation Date: Tue, 10 May 2022 02:08:20 +0800 [thread overview] Message-ID: <202205100125.ebeEi8X2-lkp@intel.com> (raw) In-Reply-To: <20220429182728.14008-2-krisman@collabora.com> Hi Gabriel, I love your patch! Perhaps something to improve: [auto build test WARNING on tytso-ext4/dev] [also build test WARNING on jaegeuk-f2fs/dev-test linus/master v5.18-rc6 next-20220509] [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] url: https://github.com/intel-lab-lkp/linux/commits/Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220430-022957 base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev config: x86_64-rhel-8.3-func (https://download.01.org/0day-ci/archive/20220510/202205100125.ebeEi8X2-lkp@intel.com/config) compiler: gcc-11 (Debian 11.2.0-20) 11.2.0 reproduce (this is a W=1 build): # https://github.com/intel-lab-lkp/linux/commit/6bf2e9e6750865e9e033adc185eacd37e8b5b0dd git remote add linux-review https://github.com/intel-lab-lkp/linux git fetch --no-tags linux-review Gabriel-Krisman-Bertazi/Clean-up-the-case-insenstive-lookup-path/20220430-022957 git checkout 6bf2e9e6750865e9e033adc185eacd37e8b5b0dd # save the config file mkdir build_dir && cp config build_dir/.config make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash fs/ext4/ fs/f2fs/ If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> All warnings (new ones prefixed by >>): fs/ext4/namei.c: In function 'ext4_match': >> fs/ext4/namei.c:1430:13: warning: unused variable 'ret' [-Wunused-variable] 1430 | int ret; | ^~~ vim +/ret +1430 fs/ext4/namei.c 1419 1420 /* 1421 * Test whether a directory entry matches the filename being searched for. 1422 * 1423 * Return: %true if the directory entry matches, otherwise %false. 1424 */ 1425 static bool ext4_match(struct inode *parent, 1426 const struct ext4_filename *fname, 1427 struct ext4_dir_entry_2 *de) 1428 { 1429 struct fscrypt_name f; > 1430 int ret; 1431 1432 if (!de->inode) 1433 return false; 1434 1435 f.usr_fname = fname->usr_fname; 1436 f.disk_name = fname->disk_name; 1437 #ifdef CONFIG_FS_ENCRYPTION 1438 f.crypto_buf = fname->crypto_buf; 1439 #endif 1440 -- 0-DAY CI Kernel Test Service https://01.org/lkp _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-05-09 18:08 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-29 18:27 [PATCH v3 0/7] Clean up the case-insenstive lookup path Gabriel Krisman Bertazi 2022-04-29 18:27 ` [f2fs-dev] " Gabriel Krisman Bertazi 2022-04-29 18:27 ` [PATCH v3 1/7] ext4: Match the f2fs ci_compare implementation Gabriel Krisman Bertazi 2022-04-29 18:27 ` [f2fs-dev] " Gabriel Krisman Bertazi 2022-05-09 18:08 ` kernel test robot [this message] 2022-05-09 18:08 ` kernel test robot 2022-04-29 18:27 ` [PATCH v3 2/7] ext4: Simplify the handling of cached insensitive names Gabriel Krisman Bertazi 2022-04-29 18:27 ` [f2fs-dev] " Gabriel Krisman Bertazi 2022-04-29 18:27 ` [PATCH v3 3/7] ext4: Implement ci comparison using unicode_name Gabriel Krisman Bertazi 2022-04-29 18:27 ` [f2fs-dev] " Gabriel Krisman Bertazi 2022-05-09 20:13 ` kernel test robot 2022-05-09 20:13 ` kernel test robot 2022-04-29 18:27 ` [PATCH v3 4/7] ext4: Simplify hash check on ext4_match Gabriel Krisman Bertazi 2022-04-29 18:27 ` [f2fs-dev] " Gabriel Krisman Bertazi 2022-04-29 18:27 ` [PATCH v3 5/7] ext4: Log error when lookup of encoded dentry fails Gabriel Krisman Bertazi 2022-04-29 18:27 ` [f2fs-dev] " Gabriel Krisman Bertazi 2022-04-29 18:27 ` [PATCH v3 6/7] ext4: Move ext4_match_ci into libfs Gabriel Krisman Bertazi 2022-04-29 18:27 ` [f2fs-dev] " Gabriel Krisman Bertazi 2022-04-29 18:27 ` [PATCH v3 7/7] f2fs: Reuse generic_ci_match for ci comparisons Gabriel Krisman Bertazi 2022-04-29 18:27 ` [f2fs-dev] " Gabriel Krisman Bertazi 2022-05-09 22:29 ` kernel test robot 2022-05-09 22:29 ` [f2fs-dev] " kernel test robot
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=202205100125.ebeEi8X2-lkp@intel.com \ --to=lkp@intel.com \ --cc=adilger.kernel@dilger.ca \ --cc=ebiggers@kernel.org \ --cc=jaegeuk@kernel.org \ --cc=kbuild-all@lists.01.org \ --cc=kernel@collabora.com \ --cc=krisman@collabora.com \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=tytso@mit.edu \ /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: linkBe 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.