public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Arpitha Raghunandan <98.arpi@gmail.com>,
	brendanhiggins@google.com, skhan@linuxfoundation.org,
	elver@google.com, yzaikin@google.com, tytso@mit.edu,
	adilger.kernel@dilger.ca, Tim.Bird@sony.com, davidgow@google.com
Cc: kbuild-all@lists.01.org, Arpitha Raghunandan <98.arpi@gmail.com>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v8 2/2] fs: ext4: Modify inode-test.c to use KUnit parameterized testing feature
Date: Mon, 16 Nov 2020 05:07:33 +0800	[thread overview]
Message-ID: <202011160555.ifjxdC7D-lkp@intel.com> (raw)
In-Reply-To: <20201115185905.169349-1-98.arpi@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2608 bytes --]

Hi Arpitha,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on ext4/dev]
[also build test WARNING on linus/master v5.10-rc3 next-20201113]
[cannot apply to tytso-fscrypt/master]
[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/0day-ci/linux/commits/Arpitha-Raghunandan/kunit-Support-for-Parameterized-Testing/20201116-030137
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
config: microblaze-randconfig-r031-20201115 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/002a7d4700bd033cceff2f2ab10bcc4a440f1377
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Arpitha-Raghunandan/kunit-Support-for-Parameterized-Testing/20201116-030137
        git checkout 002a7d4700bd033cceff2f2ab10bcc4a440f1377
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=microblaze 

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 >>):

   In function 'timestamp_expectation_to_desc',
       inlined from 'ext4_inode_gen_params' at fs/ext4/inode-test.c:223:1:
>> fs/ext4/inode-test.c:219:2: warning: 'strncpy' output truncated before terminating nul copying as many bytes from a string as its length [-Wstringop-truncation]
     219 |  strncpy(desc, t->test_case_name, desc_length);
         |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/ext4/inode-test.c: In function 'ext4_inode_gen_params':
   fs/ext4/inode-test.c:217:20: note: length computed here
     217 |  int desc_length = strlen(t->test_case_name);
         |                    ^~~~~~~~~~~~~~~~~~~~~~~~~

vim +/strncpy +219 fs/ext4/inode-test.c

   213	
   214	static void timestamp_expectation_to_desc(const struct timestamp_expectation *t,
   215						  char *desc)
   216	{
   217		int desc_length = strlen(t->test_case_name);
   218	
 > 219		strncpy(desc, t->test_case_name, desc_length);
   220		desc[desc_length] = '\0';
   221	}
   222	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30126 bytes --]

  parent reply	other threads:[~2020-11-15 21:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 18:57 [PATCH v8 1/2] kunit: Support for Parameterized Testing Arpitha Raghunandan
2020-11-15 18:59 ` [PATCH v8 2/2] fs: ext4: Modify inode-test.c to use KUnit parameterized testing feature Arpitha Raghunandan
2020-11-15 19:44   ` Marco Elver
2020-11-16  4:54     ` Arpitha Raghunandan
2020-11-15 21:07   ` kernel test robot [this message]
2020-11-30 22:24 ` [PATCH v8 1/2] kunit: Support for Parameterized Testing Brendan Higgins

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=202011160555.ifjxdC7D-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=98.arpi@gmail.com \
    --cc=Tim.Bird@sony.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=brendanhiggins@google.com \
    --cc=davidgow@google.com \
    --cc=elver@google.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tytso@mit.edu \
    --cc=yzaikin@google.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