linux-kernel - Re: [PATCH 12/14] USB: oti6858: fix DMA buffer on stack

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:	Mon, 28 Dec 2009 17:46:19 -0500
From:	Andres Salomon <dilinger@...ued.net>
To:	linux-kernel@...r.kernel.org
Cc:	linux-usb@...r.kernel.org
Subject:  Re: [PATCH 12/14] USB: oti6858: fix DMA buffer on stack

On Mon, 28 Dec 2009 23:01:56 +0100
Johan Hovold <jhovold@...il.com> wrote:

[...]
> diff --git a/drivers/usb/serial/oti6858.c
> b/drivers/usb/serial/oti6858.c index c644e26..2ae97e7 100644
> --- a/drivers/usb/serial/oti6858.c
> +++ b/drivers/usb/serial/oti6858.c
> @@ -302,7 +302,7 @@ void send_data(struct work_struct *work)
>  	struct usb_serial_port *port = priv->port;
>  	int count = 0, result;
>  	unsigned long flags;
> -	unsigned char allow;
> +	u8 *allow;
>  
>  	dbg("%s(port = %d)", __func__, port->number);
>  

Erm, am I missing something here?  You're removing a 1 byte
stack variable and replacing it with a 4 byte (pointer) stack
variable?  What's the point of that, exactly?



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