From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ildar Ismagilov <devix84@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] srcu: Prevent sdp->srcu_gp_seq_needed_exp counter wrap
Date: Sat, 3 Feb 2018 01:16:28 -0800 [thread overview]
Message-ID: <20180203091628.GF3617@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180131193954.28386-1-devix84@gmail.com>
On Wed, Jan 31, 2018 at 10:39:53PM +0300, Ildar Ismagilov wrote:
> Signed-off-by: Ildar Ismagilov <devix84@gmail.com>
I did apply this for testing and review, thank you and good eyes!
However, I had to:
1. hand-edit it to make it work against the rcu/dev
branch of my -rcu tree:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
2. fill out the commit logs.
Please see below for the updated patch, and please let me know if I
messed something up.
In the future, could you please apply your patches against the rcu/dev
branch of -rcu and provide more complete commit logs? The commit log
should describe the problem and how that problem is fixed.
Also, are you able to test these using rcutorture? If not, let's get you
set up for that, as I am prone to testing backlogs just now. Plus I am
writing this while 34,000 feet over Western Australia. So it would mean
fewer delays for you if you could test your own patches. ;-)
Thanx, Paul
------------------------------------------------------------------------
commit 753abb606ba61012c8838c73e2c888aea20efe13
Author: Ildar Ismagilov <devix84@gmail.com>
Date: Wed Jan 31 22:39:53 2018 +0300
srcu: Prevent sdp->srcu_gp_seq_needed_exp counter wrap
SRCU checks each srcu_data structure's grace-period number for counter
wrap four times per cycle by default. This frequency guarantees that
normal comparisons will detect potential wrap. However, the expedited
grace-period number is not checked. The consquences are not too horrible
(a failure to expedite a grace period when requested), but it would be
good to avoid such things. This commit therefore adds this check to
the expedited grace-period number.
Signed-off-by: Ildar Ismagilov <devix84@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
index 2878387d4189..ad3e1aa5e6ea 100644
--- a/kernel/rcu/srcutree.c
+++ b/kernel/rcu/srcutree.c
@@ -579,6 +579,9 @@ static void srcu_gp_end(struct srcu_struct *sp)
if (ULONG_CMP_GE(gpseq,
sdp->srcu_gp_seq_needed + 100))
sdp->srcu_gp_seq_needed = gpseq;
+ if (ULONG_CMP_GE(gpseq,
+ sdp->srcu_gp_seq_needed_exp + 100))
+ sdp->srcu_gp_seq_needed_exp = gpseq;
spin_unlock_irqrestore_rcu_node(sdp, flags);
}
}
next prev parent reply other threads:[~2018-02-03 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 19:39 [PATCH 1/2] srcu: Prevent sdp->srcu_gp_seq_needed_exp counter wrap Ildar Ismagilov
2018-02-03 9:16 ` Paul E. McKenney [this message]
[not found] ` <CADCZxWdVnpjS7Xqs_-tJcxLRTONrEEh8yF32F=mZUNhyj8bBfw@mail.gmail.com>
2018-02-09 12:31 ` Paul E. McKenney
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=20180203091628.GF3617@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=devix84@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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).