linux-kernel - Re: [PATCH] Declare PIO_CMAP/GIO

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: <20090216172318.GB26018@nostromo.devel.redhat.com>
Date:	Mon, 16 Feb 2009 12:23:18 -0500
From:	Bill Nottingham <notting@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Jiri Kosina <jkosina@...e.cz>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Declare PIO_CMAP/GIO_CMAP as compatbile ioctls.

(dropping trivial@ and stable@ cc's)

Andrew Morton (akpm@...ux-foundation.org) said: 
> On Wed, 11 Feb 2009 14:41:25 +0100 (CET) Jiri Kosina <jkosina@...e.cz> wrote:
> 
> > On Tue, 10 Feb 2009, Bill Nottingham wrote:
> > 
> > > Otherwise, these don't work when called from 32-bit userspace on 64-bit kernels.
> 
> Bill, please remember to add signoffs?  This should all be scripted.

I would have expected that that would be the default in 'git format-patch'.
Will keep note of that for the future.

> > Could you please give your Acked-by for it so that I can 
> > merge, or take it through your tree completely?
> 
> afaict this fix is needed all the way back to 2.6.tiny.  I merged it
> with 2.6.29 intentions.  Also tagged as needed in 2.6.25.x and later.

So, is there some way to do static analysis on the kernel source to
find *all* ioctls that aren't marked as compatible, and don't have
specific compat handlers?

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