From: Sowmini Varadhan <sowmini.varadhan@xxxxxxxxxx> Date: Tue, 23 Feb 2016 15:53:29 -0500 > On (02/23/16 22:51), mroos@xxxxxxxx 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? Of course it can have issues and contextually we have to be careful about what the code can assume about that casted 'sk' object. Your report looks legit and I was hoping Eric would chime in here with an analysis. Eric, we can't access sk->sk_policy[] on a request sock. I guess we'll have to use the sk->sk_policy[] of the parent? -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
