On Thu, Dec 14, 2017 at 12:00:42PM +0530, Ashok Kumar wrote: > Neil / Xin, > > The best way is to change the LKSTCP kernel code to handle this > situation and stop sending SCTP abort message? > > Can you please give guidance on where to change the code? > > Thanks, > Ashok > while Xin's code will have the desired effect, that is absolutely the wrong thing to do, as you don't want to suppress abort messages, you want to suppress them in the event that a process needs to be migrated to your backup system. If you're going to hack up your system like that, I'd suggest two things: 1) Use a systemtap script, or a kprobe module to hook into the code in question, that way you can keep your custom changes isolated. 2) Gate the setting of chunk to NULL on the presence of SIGKILL or SIGSEGV in the pending signals set of the task you are working on. Neil -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
