From: Sarosh Arif <sarosh.arif@emumba.com>
To: rsanford@akamai.com, erik.g.carrillo@intel.com, dev@dpdk.org
Cc: stable@dpdk.org, Sarosh Arif <sarosh.arif@emumba.com>,
h.mikita89@gmail.com
Subject: [dpdk-dev] [PATCH] lib/librte_timer:fix corruption with reset
Date: Tue, 7 Jul 2020 14:03:20 +0500 [thread overview]
Message-ID: <20200707090320.2463-1-sarosh.arif@emumba.com> (raw)
If the user tries to reset/stop some other timer in it's callback
function, which is also about to expire, using
rte_timer_reset_sync/rte_timer_stop_sync the application goes into
an infinite loop. This happens because
rte_timer_reset_sync/rte_timer_stop_sync loop until the timer
resets/stops and there is check inside timer_set_config_state which
prevents a running timer from being reset/stopped by not it's own
timer_cb. Therefore timer_set_config_state returns -1 due to which
rte_timer_reset returns -1 and rte_timer_reset_sync goes into an
infinite loop.
The soloution to this problem is to return -1 from
rte_timer_reset_sync/rte_timer_stop_sync in case the user tries to
reset/stop some other timer in it's callback function.
Bugzilla ID: 491
Fixes: 20d159f20543 ("timer: fix corruption with reset")
Cc: h.mikita89@gmail.com
Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
---
lib/librte_timer/rte_timer.c | 25 +++++++++++++++++++++++--
lib/librte_timer/rte_timer.h | 4 ++--
2 files changed, 25 insertions(+), 4 deletions(-)
diff --git a/lib/librte_timer/rte_timer.c b/lib/librte_timer/rte_timer.c
index 6d19ce469..ed48bcbfd 100644
--- a/lib/librte_timer/rte_timer.c
+++ b/lib/librte_timer/rte_timer.c
@@ -576,14 +576,24 @@ rte_timer_alt_reset(uint32_t timer_data_id, struct rte_timer *tim,
}
/* loop until rte_timer_reset() succeed */
-void
+int
rte_timer_reset_sync(struct rte_timer *tim, uint64_t ticks,
enum rte_timer_type type, unsigned tim_lcore,
rte_timer_cb_t fct, void *arg)
{
+ struct rte_timer_data *timer_data;
+ TIMER_DATA_VALID_GET_OR_ERR_RET(default_data_id, timer_data, -EINVAL);
+
+ if (tim->status.state == RTE_TIMER_RUNNING && \
+ (tim->status.owner != (uint16_t)tim_lcore || \
+ tim != timer_data->priv_timer[tim_lcore].running_tim))
+ return -1;
+
while (rte_timer_reset(tim, ticks, type, tim_lcore,
fct, arg) != 0)
rte_pause();
+
+ return 0;
}
static int
@@ -642,11 +652,22 @@ rte_timer_alt_stop(uint32_t timer_data_id, struct rte_timer *tim)
}
/* loop until rte_timer_stop() succeed */
-void
+int
rte_timer_stop_sync(struct rte_timer *tim)
{
+ struct rte_timer_data *timer_data;
+ TIMER_DATA_VALID_GET_OR_ERR_RET(default_data_id, timer_data, -EINVAL);
+ unsigned int lcore_id = rte_lcore_id();
+
+ if (tim->status.state == RTE_TIMER_RUNNING && \
+ (tim->status.owner != (uint16_t)lcore_id || \
+ tim != timer_data->priv_timer[lcore_id].running_tim))
+ return -1;
+
while (rte_timer_stop(tim) != 0)
rte_pause();
+
+ return 0;
}
/* Test the PENDING status of the timer handle tim */
diff --git a/lib/librte_timer/rte_timer.h b/lib/librte_timer/rte_timer.h
index c6b3d450d..392ca423d 100644
--- a/lib/librte_timer/rte_timer.h
+++ b/lib/librte_timer/rte_timer.h
@@ -275,7 +275,7 @@ int rte_timer_reset(struct rte_timer *tim, uint64_t ticks,
* @param arg
* The user argument of the callback function.
*/
-void
+int
rte_timer_reset_sync(struct rte_timer *tim, uint64_t ticks,
enum rte_timer_type type, unsigned tim_lcore,
rte_timer_cb_t fct, void *arg);
@@ -314,7 +314,7 @@ int rte_timer_stop(struct rte_timer *tim);
* @param tim
* The timer handle.
*/
-void rte_timer_stop_sync(struct rte_timer *tim);
+int rte_timer_stop_sync(struct rte_timer *tim);
/**
* Test if a timer is pending.
--
2.17.1
next reply other threads:[~2020-07-07 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 9:03 Sarosh Arif [this message]
2020-07-07 16:09 ` Stephen Hemminger
2020-07-08 5:06 ` [dpdk-dev] [PATCH v2] " Sarosh Arif
2020-07-08 15:07 ` Stephen Hemminger
2020-07-09 7:05 ` Sarosh Arif
2020-07-08 15:08 ` Stephen Hemminger
2020-07-09 7:02 ` Sarosh Arif
2020-07-10 6:59 ` [dpdk-dev] [PATCH v3] " Sarosh Arif
2020-07-10 15:19 ` Stephen Hemminger
2020-07-28 19:04 ` Carrillo, Erik G
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=20200707090320.2463-1-sarosh.arif@emumba.com \
--to=sarosh.arif@emumba.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=h.mikita89@gmail.com \
--cc=rsanford@akamai.com \
--cc=stable@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).