On 11/25/2015 4:52 AM, Quentin Casasnovas wrote:
On Wed, Nov 25, 2015 at 12:21:45PM +, David Laight wrote:
From: Santosh Shilimkar
Sent: 24 November 2015 22:13
...
Sasha's found a NULL pointer dereference in the RDS connection code when
sending a message to an apparently unbound socket.
On Wed, Nov 25, 2015 at 12:21:45PM +, David Laight wrote:
> From: Santosh Shilimkar
> > Sent: 24 November 2015 22:13
> ...
> > Sasha's found a NULL pointer dereference in the RDS connection code when
> > sending a message to an apparently unbound socket. The problem is caused
> > by the code c
From: Santosh Shilimkar
> Sent: 24 November 2015 22:13
...
> Sasha's found a NULL pointer dereference in the RDS connection code when
> sending a message to an apparently unbound socket. The problem is caused
> by the code checking if the socket is bound in rds_sendmsg(), which checks
> the rs_bou
From: Santosh Shilimkar
Date: Tue, 24 Nov 2015 17:13:21 -0500
> From: Quentin Casasnovas
>
> Sasha's found a NULL pointer dereference in the RDS connection code when
> sending a message to an apparently unbound socket. The problem is caused
> by the code checking if the socket is bound in rds_
From: Quentin Casasnovas
Sasha's found a NULL pointer dereference in the RDS connection code when
sending a message to an apparently unbound socket. The problem is caused
by the code checking if the socket is bound in rds_sendmsg(), which checks
the rs_bound_addr field without taking a lock on t
