linux-kernel - Re: [PATCH 2/2] iov_iter: use bvec iterator to implement iterate

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] [day] [month] [year] [list]

Date:	Sat, 10 Oct 2015 23:48:01 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	kbuild test robot <lkp@...el.com>
Cc:	kbuild-all@...org, Jens Axboe <axboe@...nel.dk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH 2/2] iov_iter: use bvec iterator to implement iterate_bvec()

On Sat, Oct 10, 2015 at 11:33 PM, kbuild test robot <lkp@...el.com> wrote:
> Hi Ming,
>
> [auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore]
>
> config: i386-randconfig-s1-201540 (attached as .config)
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
>    lib/iov_iter.c: In function 'copy_to_iter':
>>> lib/iov_iter.c:61:19: error: storage size of '__bi' isn't known
>      struct bvec_iter __bi, __start;   \
>                       ^
>    lib/iov_iter.c:97:3: note: in expansion of macro 'iterate_bvec'
>       iterate_bvec(i, n, v, bvec, skip, (B))  \

The warning is because CONFIG_BLOCK is disabled, maybe
bvec iterator helpers still need to include even though CONFIG_BLOCK
is disabled.


-- 
Ming Lei
--
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/