lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 2 Feb 2016 11:22:56 +0800
From:	kbuild test robot <lkp@...el.com>
To:	Bean Huo <jackyard88@...il.com>
Cc:	kbuild-all@...org, richard@....at, dedekind1@...il.com,
	adrian.hunter@...el.com, computersforpeace@...il.com,
	boris.brezillon@...e-electrons.com, beanhuo@...ron.com,
	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
	zszubbocsev@...ron.com, peterpandong@...ron.com
Subject: Re: [PATCH v2 14/17] drivers:mtd:ubi:add backup operation in
 ubi_io_write

Hi Bean,

[auto build test WARNING on v4.5-rc2]
[also build test WARNING on next-20160201]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Bean-Huo/Add-a-bakvol-module-in-UBI-layer-for-MLC-paired-page-power-loss-issue/20160202-104450
config: x86_64-randconfig-x012-201605 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   drivers/mtd/ubi/io.c: In function 'ubi_io_write':
>> drivers/mtd/ubi/io.c:242:6: warning: unused variable 'skip' [-Wunused-variable]
     int skip;
         ^

vim +/skip +242 drivers/mtd/ubi/io.c

   226	 *
   227	 * This function writes @len bytes of data from buffer @buf to offset @offset
   228	 * of physical eraseblock @pnum. If all the data were successfully written,
   229	 * zero is returned. If an error occurred, this function returns a negative
   230	 * error code. If %-EIO is returned, the physical eraseblock most probably went
   231	 * bad.
   232	 *
   233	 * Note, in case of an error, it is possible that something was still written
   234	 * to the flash media, but may be some garbage.
   235	 */
   236	int ubi_io_write(struct ubi_device *ubi, const void *buf, int pnum, int offset,
   237			 int len, int safeguard)
   238	{
   239		int err;
   240		size_t retlen;
   241		loff_t addr;
 > 242		int skip;
   243	
   244		dbg_io("write %d bytes to PEB %d:%d", len, pnum, offset);
   245	
   246		ubi_assert(pnum >= 0 && pnum < ubi->peb_count);
   247		ubi_assert(offset >= 0 && offset + len <= ubi->peb_size);
   248		ubi_assert(offset % ubi->hdrs_min_io_size == 0);
   249		ubi_assert(len > 0 && len % ubi->hdrs_min_io_size == 0);
   250	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

Download attachment ".config.gz" of type "application/octet-stream" (20303 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ