On Mon, 26 Jun 2017 17:52:30 -0400 Daniel Micay <danielmicay@xxxxxxxxx> wrote: > On Mon, 2017-06-26 at 14:45 -0700, Andrew Morton wrote: > > On Sun, 25 Jun 2017 09:16:32 +0800 kbuild test robot <fengguang.wu@int > > el.com> wrote: > > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.g > > > it for-next/fortify > > > head: d481d95b725d2abc7ed31f2f8c4c95c2bd8b0282 > > > commit: d481d95b725d2abc7ed31f2f8c4c95c2bd8b0282 [8/8] > > > include/linux/string.h: add the option of fortified string.h > > > functions > > > config: i386-allmodconfig (attached as .config) > > > compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 > > > reproduce: > > > git checkout d481d95b725d2abc7ed31f2f8c4c95c2bd8b0282 > > > # save the attached .config to linux build tree > > > make ARCH=i386 > > > > > > All errors (new ones prefixed by >>): > > > > > > In file included from arch/x86/include/asm/page_32.h:34:0, > > > from arch/x86/include/asm/page.h:13, > > > from arch/x86/include/asm/thread_info.h:11, > > > from include/linux/thread_info.h:37, > > > from arch/x86/include/asm/preempt.h:6, > > > from include/linux/preempt.h:80, > > > from include/linux/spinlock.h:50, > > > from include/linux/mmzone.h:7, > > > from include/linux/gfp.h:5, > > > from include/linux/slab.h:14, > > > from drivers/scsi/csiostor/csio_lnode.c:37: > > > In function 'memcpy', > > > inlined from 'csio_append_attrib' at > > > drivers/scsi/csiostor/csio_lnode.c:248:2, > > > > hm, this was added by Kees's 42c335f7e6702 ("scsi: csiostor: Avoid > > content leaks and casts"). > > > > I think I'll tend to ignore these odd stragglers now - a few more will > > probably pop up and we can fix them after 4.13-rc1 as they are > > reported. > > It's in the scsi for-next tree. The issue that we ran into with fortify > in the kspp tree was that scsi was merged into next after it so tests > still ran into this. I assume that for 4.13-rc1 they'll both be merged > so there shouldn't be a problem then. I'm not very familiar with how the > workflow works or how issues like this should be handled. I've staged this patchset after all the linux-next trees, so during the merge window I'll be waiting until all the depended-upon trees have merged before sending this series into Linus. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
