linux-kernel - Re: linux framebuffer ioctls

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]

Message-ID: <71a0d6ff0608241022w1101ae2bm1e9dc361f15c137c@mail.gmail.com>
Date:	Thu, 24 Aug 2006 21:22:44 +0400
From:	"Alexander Shishkin" <alexander.shishckin@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux framebuffer ioctls

On 8/24/06, Alexander Shishkin <alexander.shishckin@...il.com> wrote:
> I've just stumbled upon a funny issue regarding FBIOGET_FSCREENINFO
To answer my own question. Now that I traced the codepaths of
compat_ioctl, I see that this particular problem has been worked
around by calling do_screeninfo_to_user() which resided in
fs/compat_ioctl.c (as of 2.6.14) and now moved to
drivers/video/fbmem.c where it actually belongs.
The problem in my case was my incorrect implementation of compat_ioctl
method in my driver that called filp->f_op->ioctl() for that matter.
Stupid me.
Just in case someone ever needs this.

-- 
I am free of all prejudices. I hate every one equally.
-
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/