{"push_id":1232397498,"size":1,"distinct_size":1,"ref":"refs/heads/6.0.1","head":"82c46be14ec16e90f6bcaaad4ae6de8538808a5e","before":"1647b1bfd969c1111e3e359f15df876671b3a92f","commits":[{"sha":"82c46be14ec16e90f6bcaaad4ae6de8538808a5e","author":{"name":"Neil Horman","email":"490c3644041cdec787fa30a5cd5c4dcfde13be34@tuxdriver.com"},"message":"sctp: fully initialize sctp_outq in sctp_outq_init\n\n[ Upstream commit c5c7774d7eb4397891edca9ebdf750ba90977a69 ]\n\nIn commit 2f94aabd9f6c925d77aecb3ff020f1cc12ed8f86\n(refactor sctp_outq_teardown to insure proper re-initalization)\nwe modified sctp_outq_teardown to use sctp_outq_init to fully re-initalize the\noutq structure.  Steve West recently asked me why I removed the q->error = 0\ninitalization from sctp_outq_teardown.  I did so because I was operating under\nthe impression that sctp_outq_init would properly initalize that value for us,\nbut it doesn't.  sctp_outq_init operates under the assumption that the outq\nstruct is all 0's (as it is when called from sctp_association_init), but using\nit in __sctp_outq_teardown violates that assumption. We should do a memset in\nsctp_outq_init to ensure that the entire structure is in a known state there\ninstead.\n\nSigned-off-by: Neil Horman <nhorman@tuxdriver.com>\nReported-by: \"West, Steve (NSN - US/Fort Worth)\" <steve.west@nsn.com>\nCC: Vlad Yasevich <vyasevich@gmail.com>\nCC: netdev@vger.kernel.org\nCC: davem@davemloft.net\nAcked-by: Vlad Yasevich <vyasevich@gmail.com>\nSigned-off-by: David S. Miller <davem@davemloft.net>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/dblockopp/G3_CooCoo_Kernel/commits/82c46be14ec16e90f6bcaaad4ae6de8538808a5e"}]}
{"actor":{"display_login":"dblockopp"}}