[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20101028.114941.39177249.davem@davemloft.net>
Date: Thu, 28 Oct 2010 11:49:41 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: andy.grover@...cle.com
Cc: torvalds@...ux-foundation.org, jon.maloy@...csson.com,
netdev@...r.kernel.org, drosenberg@...curity.com,
security@...nel.org, allan.stephens@...driver.com,
rds-devel@....oracle.com
Subject: Re: [Security] TIPC security issues
From: Andy Grover <andy.grover@...cle.com>
Date: Thu, 28 Oct 2010 11:45:04 -0700
> Yes that's right, it's to map a memory region that will be the target
> of an RDMA operation. I don't know why struct rds_iovec was used
> instead of struct iovec, but I think we're stuck, since it's part of
> our socket API.
>
> I'll send DaveM patches to fix those two immediately-identified
> problems today, and we'll take a good long look at the rest of the
> code for further issues.
FWIW, I would strongly suggest that you copy the iovecs into the
kernel before parsing them like sys_sendmsg() and sys_recvmsg() do in
net/socket.c as part of these fixes.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists