linux-kernel - Build failures in -next due to commit "asm-generic: {get,put}

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

Message-ID: <55AD5265.5070109@roeck-us.net>
Date:	Mon, 20 Jul 2015 12:56:21 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Yoshinori Sato <ysato@...rs.sourceforge.jp>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Arnd Bergmann <arnd@...db.de>,
	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
	Jens Axboe <axboe@...nel.dk>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>
Subject: Build failures in -next due to commit "asm-generic: {get,put}_user
 ptr argument evaluate only 1 time"

Hi,

Commit 52b2512d507d ("asm-generic: {get,put}_user ptr argument evaluate only 1 time")
causes the following compile error with various architectures (arc, arcv2, c6x, hexagon,
um, unicore32) in -next.

block/scsi_ioctl.c: In function ‘sg_scsi_ioctl’:
block/scsi_ioctl.c:436:2: error: invalid initializer
   if (get_user(opcode, sic->data))
   ^
make[1]: *** [block/scsi_ioctl.o] Error 1

A possible fix would be to use &sic->data[0] instead, but I am not sure if this change
in semantics of get_user would be acceptable.

Another failure due to the same commit is seen when building arc:axs103_defconfig.

fs/fat/dir.c: In function ‘fat_ioctl_filldir’:
fs/fat/dir.c:752:43: error: invalid initializer
  FAT_IOCTL_FILLDIR_FUNC(fat_ioctl_filldir, __fat_dirent)

This error is related to the put_user changes. No idea how to fix that one.

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