linux-kernel - Re: [PATCH] scsi: kconfig: When possible, compile drivers with COMPILE

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]

Message-ID: <201510150911.LUZUzevd%fengguang.wu@intel.com>
Date:	Thu, 15 Oct 2015 09:11:13 +0800
From:	kbuild test robot <lkp@...el.com>
To:	Luis de Bethencourt <luisbg@....samsung.com>
Cc:	kbuild-all@...org, linux-kernel@...r.kernel.org,
	JBottomley@...n.com, linux-scsi@...r.kernel.org,
	Luis de Bethencourt <luisbg@....samsung.com>
Subject: Re: [PATCH] scsi: kconfig: When possible, compile drivers with
 COMPILE_TEST

Hi Luis,

[auto build test WARNING on scsi/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Luis-de-Bethencourt/scsi-kconfig-When-possible-compile-drivers-with-COMPILE_TEST/20151015-051558
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/scsi/NCR5380.c:1751:9: sparse: context imbalance in 'NCR5380_transfer_dma' - unexpected unlock

vim +/NCR5380_transfer_dma +1751 drivers/scsi/NCR5380.c

^1da177e Linus Torvalds 2005-04-16  1735  	NCR5380_setup(instance);
^1da177e Linus Torvalds 2005-04-16  1736  
^1da177e Linus Torvalds 2005-04-16  1737  	if ((tmp = (NCR5380_read(STATUS_REG) & PHASE_MASK)) != p) {
^1da177e Linus Torvalds 2005-04-16  1738  		*phase = tmp;
^1da177e Linus Torvalds 2005-04-16  1739  		return -1;
^1da177e Linus Torvalds 2005-04-16  1740  	}
^1da177e Linus Torvalds 2005-04-16  1741  #if defined(REAL_DMA) || defined(REAL_DMA_POLL)
^1da177e Linus Torvalds 2005-04-16  1742  #ifdef READ_OVERRUNS
^1da177e Linus Torvalds 2005-04-16  1743  	if (p & SR_IO) {
^1da177e Linus Torvalds 2005-04-16  1744  		c -= 2;
^1da177e Linus Torvalds 2005-04-16  1745  	}
^1da177e Linus Torvalds 2005-04-16  1746  #endif
52a6a1cb Finn Thain     2014-03-18  1747  	dprintk(NDEBUG_DMA, "scsi%d : initializing DMA channel %d for %s, %d bytes %s %0x\n", instance->host_no, instance->dma_channel, (p & SR_IO) ? "reading" : "writing", c, (p & SR_IO) ? "to" : "from", (unsigned) d);
^1da177e Linus Torvalds 2005-04-16  1748  	hostdata->dma_len = (p & SR_IO) ? NCR5380_dma_read_setup(instance, d, c) : NCR5380_dma_write_setup(instance, d, c);
^1da177e Linus Torvalds 2005-04-16  1749  #endif
^1da177e Linus Torvalds 2005-04-16  1750  
^1da177e Linus Torvalds 2005-04-16 @1751  	NCR5380_write(TARGET_COMMAND_REG, PHASE_SR_TO_TCR(p));
^1da177e Linus Torvalds 2005-04-16  1752  
^1da177e Linus Torvalds 2005-04-16  1753  #ifdef REAL_DMA
^1da177e Linus Torvalds 2005-04-16  1754  	NCR5380_write(MODE_REG, MR_BASE | MR_DMA_MODE | MR_ENABLE_EOP_INTR | MR_MONITOR_BSY);
^1da177e Linus Torvalds 2005-04-16  1755  #elif defined(REAL_DMA_POLL)
^1da177e Linus Torvalds 2005-04-16  1756  	NCR5380_write(MODE_REG, MR_BASE | MR_DMA_MODE);
^1da177e Linus Torvalds 2005-04-16  1757  #else
^1da177e Linus Torvalds 2005-04-16  1758  	/*
^1da177e Linus Torvalds 2005-04-16  1759  	 * Note : on my sample board, watch-dog timeouts occurred when interrupts

:::::: The code at line 1751 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2

:::::: TO: Linus Torvalds <torvalds@...970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@...970.osdl.org>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/