From: "tip-bot for Paul E. McKenney" <tipbot@zytor•com>
To: linux-tip-commits@vger•kernel.org
Cc: tglx@linutronix•de, john.fastabend@gmail•com, mingo@kernel•org,
hpa@zytor•com, netdev@vger•kernel.org, daniel@iogearbox•net,
davem@davemloft•net, paulmck@linux•ibm.com
Subject: [tip:core/rcu] net/core/skmsg: Replace call_rcu_sched() with call_rcu()
Date: Tue, 4 Dec 2018 14:53:25 -0800 [thread overview]
Message-ID: <tip-0245b80e284d4fdabbf50589180482dc4d2cf277@git.kernel.org> (raw)
Commit-ID: 0245b80e284d4fdabbf50589180482dc4d2cf277
Gitweb: https://git.kernel.org/tip/0245b80e284d4fdabbf50589180482dc4d2cf277
Author: Paul E. McKenney <paulmck@linux•ibm.com>
AuthorDate: Wed, 7 Nov 2018 15:09:25 -0800
Committer: Paul E. McKenney <paulmck@linux•ibm.com>
CommitDate: Sat, 1 Dec 2018 12:38:50 -0800
net/core/skmsg: Replace call_rcu_sched() with call_rcu()
Now that call_rcu()'s callback is not invoked until after all
preempt-disable regions of code have completed (in addition to explicitly
marked RCU read-side critical sections), call_rcu() can be used in place
of call_rcu_sched(). This commit therefore makes that change.
Signed-off-by: Paul E. McKenney <paulmck@linux•ibm.com>
Cc: John Fastabend <john.fastabend@gmail•com>
Cc: Daniel Borkmann <daniel@iogearbox•net>
Cc: "David S. Miller" <davem@davemloft•net>
Cc: <netdev@vger•kernel.org>
---
net/core/skmsg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/core/skmsg.c b/net/core/skmsg.c
index 56a99d0c9aa0..c92d6ccce610 100644
--- a/net/core/skmsg.c
+++ b/net/core/skmsg.c
@@ -580,7 +580,7 @@ void sk_psock_drop(struct sock *sk, struct sk_psock *psock)
write_unlock_bh(&sk->sk_callback_lock);
sk_psock_clear_state(psock, SK_PSOCK_TX_ENABLED);
- call_rcu_sched(&psock->rcu, sk_psock_destroy);
+ call_rcu(&psock->rcu, sk_psock_destroy);
}
EXPORT_SYMBOL_GPL(sk_psock_drop);
reply other threads:[~2018-12-04 22:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tip-0245b80e284d4fdabbf50589180482dc4d2cf277@git.kernel.org \
--to=tipbot@zytor$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=hpa@zytor$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-tip-commits@vger$(echo .)kernel.org \
--cc=mingo@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulmck@linux$(echo .)ibm.com \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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