From: "Jere Leppänen" <jere.leppanen@nokia.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [PATCHv2] sctp: Don't add the shutdown timer if its already been added
Date: Tue, 19 May 2020 08:51:23 +0000 [thread overview]
Message-ID: <alpine.LFD.2.21.2005191146330.774972@sut4-server4-pub.sut-1.archcommon.nsn-rdnet.net> (raw)
In-Reply-To: <1458334046-26323-1-git-send-email-nhorman@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 2503 bytes --]
On Thu, 30 Apr 2020, Marcelo Ricardo Leitner wrote:
> On Wed, Apr 29, 2020 at 07:36:13AM -0400, Neil Horman wrote:
> > This BUG halt was reported a while back, but the patch somehow got
> > missed:
> >
> > PID: 2879 TASK: c16adaa0 CPU: 1 COMMAND: "sctpn"
> > #0 [f418dd28] crash_kexec at c04a7d8c
> > #1 [f418dd7c] oops_end at c0863e02
> > #2 [f418dd90] do_invalid_op at c040aaca
> > #3 [f418de28] error_code (via invalid_op) at c08631a5
> > EAX: f34baac0 EBX: 00000090 ECX: f418deb0 EDX: f5542950 EBP: 00000000
> > DS: 007b ESI: f34ba800 ES: 007b EDI: f418dea0 GS: 00e0
> > CS: 0060 EIP: c046fa5e ERR: ffffffff EFLAGS: 00010286
> > #4 [f418de5c] add_timer at c046fa5e
> > #5 [f418de68] sctp_do_sm at f8db8c77 [sctp]
> > #6 [f418df30] sctp_primitive_SHUTDOWN at f8dcc1b5 [sctp]
> > #7 [f418df48] inet_shutdown at c080baf9
> > #8 [f418df5c] sys_shutdown at c079eedf
> > #9 [f418df70] sys_socketcall at c079fe88
> > EAX: ffffffda EBX: 0000000d ECX: bfceea90 EDX: 0937af98
> > DS: 007b ESI: 0000000c ES: 007b EDI: b7150ae4
> > SS: 007b ESP: bfceea7c EBP: bfceeaa8 GS: 0033
> > CS: 0073 EIP: b775c424 ERR: 00000066 EFLAGS: 00000282
> >
> > It appears that the side effect that starts the shutdown timer was processed
> > multiple times, which can happen as multiple paths can trigger it. This of
> > course leads to the BUG halt in add_timer getting called.
> >
> > Fix seems pretty straightforward, just check before the timer is added if its
> > already been started. If it has mod the timer instead to min(current
> > expiration, new expiration)
> >
> > Its been tested but not confirmed to fix the problem, as the issue has only
> > occured in production environments where test kernels are enjoined from being
> > installed. It appears to be a sane fix to me though. Also, recentely,
> > Jere found a reproducer posted on list to confirm that this resolves the
> > issues
> >
> > Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> > CC: Vlad Yasevich <vyasevich@gmail.com>
> > CC: "David S. Miller" <davem@davemloft.net>
> > CC: Jere Leppänen <jere.leppanen@nokia.com>
> > CC: marcelo.leitner@gmail.com
> >
> > ---
> > Change notes:
> > V2) Updated to use timer_reduce
>
> Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Hey is this patch falling through the cracks again? No rush, I'm just
wondering what's going on.
next prev parent reply other threads:[~2020-05-19 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 20:47 [PATCHv2] sctp: Don't add the shutdown timer if its already been added Neil Horman
2016-03-18 20:53 ` marcelo.leitner
2016-03-21 11:31 ` Neil Horman
2020-04-29 11:36 ` Neil Horman
2020-04-30 8:54 ` Jere Leppänen
2020-04-30 10:59 ` Neil Horman
2020-04-30 13:59 ` Marcelo Ricardo Leitner
2020-05-19 8:51 ` Jere Leppänen [this message]
2020-05-19 19:24 ` Marcelo Ricardo Leitner
2020-05-19 19:59 ` Neil Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.21.2005191146330.774972@sut4-server4-pub.sut-1.archcommon.nsn-rdnet.net \
--to=jere.leppanen@nokia.com \
--cc=linux-sctp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.