Re: [PATCH] [sparse] ip_rt_ioctl argument is user pointer

netdev

Re: [PATCH] [sparse] ip_rt_ioctl argument is user pointer

To:	Stephen Hemminger <shemminger@xxxxxxxx>
Subject:	Re: [PATCH] [sparse] ip_rt_ioctl argument is user pointer
From:	"David S. Miller" <davem@xxxxxxxxxx>
Date:	Tue, 22 Jun 2004 17:11:29 -0700
Cc:	netdev@xxxxxxxxxxx
In-reply-to:	<20040622160022.75db69bb@dell_ss3.pdx.osdl.net>
References:	<20040622160022.75db69bb@dell_ss3.pdx.osdl.net>
Sender:	netdev-bounce@xxxxxxxxxxx

On Tue, 22 Jun 2004 16:00:22 -0700
Stephen Hemminger <shemminger@xxxxxxxx> wrote:

> The function ip_rt_ioctl expects a pointer to a user route structure, so 
> define
> it that way and cast as appropriate.

Applied, thanks Stephen.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH] [sparse] ip_rt_ioctl argument is user pointer, Stephen Hemminger Re: [PATCH] [sparse] ip_rt_ioctl argument is user pointer, David S. Miller <=

Previous by Date:	Re: [PATCH] [sparse] rtentry->rt_dev is __user, David S. Miller
Next by Date:	RE: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out+ delayscheduler, Venkatesan, Ganesh
Previous by Thread:	[PATCH] [sparse] ip_rt_ioctl argument is user pointer, Stephen Hemminger
Next by Thread:	[RFT] convert syskonnect gigabit ether driver to PCI module interface, Stephen Hemminger
Indexes:	[Date] [Thread] [Top] [All Lists]