linux-kernel - Re: [patch 03/11] GRU Driver - driver internal header files

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: <20080610145711.GB29042@sgi.com>
Date:	Tue, 10 Jun 2008 09:57:11 -0500
From:	Jack Steiner <steiner@....com>
To:	Roland Dreier <rdreier@...co.com>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org, mingo@...e.hu,
	tglx@...utronix.de, holt@....com, andrea@...ranet.com
Subject: Re: [patch 03/11] GRU Driver - driver internal header files

On Mon, Jun 09, 2008 at 02:38:18PM -0700, Roland Dreier wrote:
>  > +/*
>  > + * Structure used to pass TLB flush parameters to the driver
>  > + */
>  > +struct gru_flush_tlb_req {
>  > +	unsigned long	gseg;
>  > +	unsigned long	vaddr;
>  > +	size_t		len;
>  > +};
> 
> This and other data structures you pass into the kernel via ioctl() are
> not 32/64 clean.  So a 32-bit process (which can easily run on a 64-bit
> x86-64 kernel) will end up sending garbage to the kernel.

Good point in general but I don't this this will be an issue for us.
The data structures are used only in libgru.so - a library used to
externalize the GRU to user applications.  We will provide only -64
bit versions of this library.

If an abusive -32 bit application _tried_ to issue the system calls, the
parameters should fail the validity checking in the driver.


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