From: Jes Sorensen <jes.sorensen@gmail.com>
To: minyard@acm.org
Cc: linux-kernel@vger.kernel.org,
openipmi-developer@lists.sourceforge.net, kernel-team@fb.com
Subject: [PATCH 1/1] ipmi_si_intf: Fix race in timer shutdown handling
Date: Wed, 28 Aug 2019 16:36:25 -0400 [thread overview]
Message-ID: <20190828203625.32093-2-Jes.Sorensen@gmail.com> (raw)
In-Reply-To: <20190828203625.32093-1-Jes.Sorensen@gmail.com>
From: Jes Sorensen <jsorensen@fb.com>
smi_mod_timer() enables the timer before setting timer_running. This
means the timer can be running when we get to stop_timer_and_thread()
without timer_running having been set, resulting in del_timer_sync()
not being called and the timer being left to cause havoc during
shutdown.
Instead just call del_timer_sync() unconditionally
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
---
drivers/char/ipmi/ipmi_si_intf.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/char/ipmi/ipmi_si_intf.c b/drivers/char/ipmi/ipmi_si_intf.c
index da5b6723329a..53425e25ecf4 100644
--- a/drivers/char/ipmi/ipmi_si_intf.c
+++ b/drivers/char/ipmi/ipmi_si_intf.c
@@ -1828,8 +1828,7 @@ static inline void stop_timer_and_thread(struct smi_info *smi_info)
}
smi_info->timer_can_start = false;
- if (smi_info->timer_running)
- del_timer_sync(&smi_info->si_timer);
+ del_timer_sync(&smi_info->si_timer);
}
static struct smi_info *find_dup_si(struct smi_info *info)
--
2.21.0
next prev parent reply other threads:[~2019-08-28 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 20:36 [PATCH 0/1] Fix race in ipmi timer cleanup Jes Sorensen
2019-08-28 20:36 ` Jes Sorensen [this message]
2019-08-28 22:32 ` Corey Minyard
2019-08-29 0:53 ` Jes Sorensen
2019-08-29 18:15 ` Corey Minyard
2019-09-15 1:08 ` [Openipmi-developer] " Corey Minyard
2019-09-16 14:01 ` Jes Sorensen
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=20190828203625.32093-2-Jes.Sorensen@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®