linux-kernel - Re: [Bug 14537] New: missing compat_ioctl on x86

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]

Message-Id: <200911042312.52116.rjw@sisk.pl>
Date:	Wed, 4 Nov 2009 23:12:52 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Thierry Vignaud <tvignaud@...driva.com>,
	bugzilla-daemon@...zilla.kernel.org
Subject: Re: [Bug 14537] New: missing compat_ioctl on x86_64

On Wednesday 04 November 2009, Thomas Gleixner wrote:
> B1;2005;0c(switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
> 
> On Tue, 3 Nov 2009, bugzilla-daemon@...zilla.kernel.org wrote:
> 
> > http://bugzilla.kernel.org/show_bug.cgi?id=14537
> > 
> >            Summary: missing compat_ioctl on x86_64
> >            Product: Platform Specific/Hardware
> >            Version: 2.5
> >           Platform: All
> >         OS/Version: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: normal
> >           Priority: P1
> >          Component: x86-64
> >         AssignedTo: platform_x86_64@...nel-bugs.osdl.org
> >         ReportedBy: tvignaud@...driva.com
> >         Regression: No
> > 
> > 
> > I used to run 64bit userspace on 64bit kernel but I recently tried to run a
> > 64bit kernel with as minimal as possible as 64bit userspace (that is
> > rpm+glibc+... in order to mananage 64bit kernel packages).
> > 
> > This revealed several missing compat_ioctl.
> > Running 32bit gnome-terminal on a 64 bit kernel results in the following in
> > dmesg:
> > 
> > - with gnome-terminal:
> > ioctl32(gnome-terminal:1755): Unknown cmd fd(19) cmd(0000530b){t:'S';sz:0}
> > arg(48111345) on /dev/pts/0
> > ioctl32(gnome-terminal:1755): Unknown cmd fd(19) cmd(0000530b){t:'S';sz:0}
> > arg(4811134a) on /dev/pts/0
> > ioctl32(gnome-terminal:1755): Unknown cmd fd(19) cmd(0000530b){t:'S';sz:0}
> > arg(48111351) on /dev/pts/0
> 
> That looks more like an application problem. 'S' is SNDRV_SEQ_IOCTL
> which has no ioctl nr 0xb. Also I have no idea why a sound sequencer
> ioctl should work on /dev/pts/0 :)
> 
> > - with X:
> > ioctl32(X:2803): Unknown cmd fd(0) cmd(40086408){t:'d';sz:8} arg(ff840a68) on
> > /var/log/Xorg.0.log
> > ioctl32(X:2803): Unknown cmd fd(0) cmd(40086408){t:'d';sz:8} arg(ff840a68) on
> > /var/log/Xorg.0.log
> 
> 'd' is used by pcmcia and DRM. DRM sounds more likely for X, but I
> have a hard time to understand why a DRM ioctl should work on
> /var/log/Xorg.0.log :)
> 
> For both gnome-terminal and X strace should tell you more.
> 
> > - when trying to suspend:
> > ioctl32(s2disk:8164): Unknown cmd fd(4) cmd(400c330d){t:'3';sz:12}
> > arg(ffc190ec) on /dev/snapshot
> > ioctl32(s2disk:8164): Unknown cmd fd(4) cmd(4004330a){t:'3';sz:4} arg(00000806)
> > on /dev/snapshot
> 
> snapshot_ioctl seems to lack compat support completely. Raphael ??

It does, but that wouldn't work anyway.  s2disk is one of the things that have
to be native.

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