[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160223205329.GD4941@oracle.com>
Date: Tue, 23 Feb 2016 15:53:29 -0500
From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
To: mroos@...ux.ee
Cc: David Miller <davem@...emloft.net>, sparclinux@...r.kernel.org,
edumazet@...gle.com, netdev@...r.kernel.org
Subject: Re: Invalid sk_policy[] access
On (02/23/16 22:51), mroos@...ux.ee wrote:
> Since there are no config-dependent difference in the struct, maybe it's
> a compiler version difference for padding/optimization instead?
possibly. The v440 is using a Debian 4.6.3-14 gcc, while the
T5 is using "4.4.7 20120313 (Red Hat 4.4.7-4)"
But my question from the email remains. Unless I am missing
something subtle in the code, a struct request_sock and a
struct sock only have the sock_common part in common. So casting
a request_sock as a struct sock may have issues?
--Sowmini
Powered by blists - more mailing lists