linux-kernel - Re: [PATCH 04/13] lib/vsprintf.c: expand field

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:	Wed, 21 Oct 2015 10:54:04 +0200
From:	Rasmus Villemoes <linux@...musvillemoes.dk>
To:	kbuild test robot <lkp@...el.com>
Cc:	kbuild-all@...org, Andrew Morton <akpm@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>, Joe Perches <joe@...ches.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 04/13] lib/vsprintf.c: expand field_width to 24 bits

On Wed, Oct 21 2015, kbuild test robot <lkp@...el.com> wrote:

> Hi Rasmus,
>
> [auto build test ERROR on next-20151020 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
>
> url:    https://github.com/0day-ci/linux/commits/Rasmus-Villemoes/lib-vsprintf-c-pull-out-padding-code-from-dentry_name/20151021-043621
> config: frv-defconfig (attached as .config)
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         make.cross ARCH=frv 

OK, apparently we need to tell gcc explicitly to pack it on frv. I've
reproduced using the above instructions, and adding __packed solves
it. Please use the alternative patch I'll send as a follow-up in a
moment.

I have to say, this automated build testing before the patches hit
-next (indeed, almost before git send-email is finished sending out the
entire series!) is rather awesome.

Rasmus
--
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/