Hi John, On Mon, Oct 18, 2021 at 04:29:58PM -0500, john.p.donnelly@xxxxxxxxxx wrote: > Call Trace: > skb_put+0x4c/0x4c > sctp_addto_chunk+0x59/0xb0 [sctp] > sctp_make_strreset_req+0x166/0x180 [sctp] > sctp_send_reset_streams+0x14d/0x300 [sctp] > sctp_setsockopt.part.21+0x101f/0x1720 [sctp] > sctp_setsockopt+0x99/0xb0 [sctp] > sock_common_setsockopt+0x1a/0x1c > SyS_setsockopt+0x86/0xe6 > +0x79/0x1ae > entry_SYSCALL_64_after_hwframe+0x151/0x0 > RIP: 0033:0x7f80bdc21be9 > > > I am not familar with any of the sctp subsystem. It was found running the > syzkaller fuzzing test suite. > > If there is a more appropriate place to report this I can do that too. This Here is fine :) > test fails on just about every 4.x and 5.x kernel. It is not > unique to 5.4. Did the test kernels include commit "sctp: account stream padding length for reconf chunk"? It is a recent fix right on this topic. It should be fixed by it, actually. Marcelo
