linux-kernel - Re: ioctl32: Unknown cmd

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:	17 Oct 2007 02:25:20 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	David Miller <davem@...emloft.net>
Cc:	arnd@...db.de, Geert.Uytterhoeven@...ycom.com,
	linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org,
	jens.axboe@...cle.com
Subject: Re: ioctl32: Unknown cmd

David Miller <davem@...emloft.net> writes:

> From: Arnd Bergmann <arnd@...db.de>
> Date: Tue, 16 Oct 2007 21:50:35 +0200
> 
> > The one point where it is expected to have changed now is when you
> > try to do these ioctls on something that is not a block device. Are
> > you sure that the files you tried them on were created correctly?
> 
> Many many many programs do this exact sort of thing.
> 
> It is one of the bad aspects of moving the compat handling
> down into the file ops for a specific device.

When this happens one should add respective IGNORE_IOCTL()s to 
compat_ioctl.c

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