From: madhuparnabhowmik04@gmail.com To: dennis.dalessandro@intel.com, mike.marciniszyn@intel.com, dledford@redhat.com, paulmck@kernel.org Cc: rcu@vger.kernel.org, joel@joelfernandes.org, frextrite@gmail.com, linux-kernel-mentees@lists.linuxfoundation.org, linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com> Subject: [PATCH 2/3] infiniband: hw: qib: qib_verbs: Use built-in RCU list checking Date: Wed, 8 Jan 2020 01:00:39 +0530 [thread overview] Message-ID: <20200107193039.22836-1-madhuparnabhowmik04@gmail.com> (raw) From: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com> Use built-in RCU and lock checking for list_for_each_entry_rcu by passing cond argument to it. Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com> --- drivers/infiniband/hw/qib/qib_verbs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/infiniband/hw/qib/qib_verbs.c b/drivers/infiniband/hw/qib/qib_verbs.c index 33778d451b82..845ba888734e 100644 --- a/drivers/infiniband/hw/qib/qib_verbs.c +++ b/drivers/infiniband/hw/qib/qib_verbs.c @@ -329,7 +329,8 @@ void qib_ib_rcv(struct qib_ctxtdata *rcd, void *rhdr, void *data, u32 tlen) if (mcast == NULL) goto drop; this_cpu_inc(ibp->pmastats->n_multicast_rcv); - list_for_each_entry_rcu(p, &mcast->qp_list, list) + list_for_each_entry_rcu(p, &mcast->qp_list, list, + lock_is_held(&(ibp->rvp.lock).dep_map)) qib_qp_rcv(rcd, hdr, 1, data, tlen, p->qp); /* * Notify rvt_multicast_detach() if it is waiting for us -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: madhuparnabhowmik04@gmail.com To: dennis.dalessandro@intel.com, mike.marciniszyn@intel.com, dledford@redhat.com, paulmck@kernel.org Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, rcu@vger.kernel.org, joel@joelfernandes.org, linux-kernel-mentees@lists.linuxfoundation.org Subject: [Linux-kernel-mentees] [PATCH 2/3] infiniband: hw: qib: qib_verbs: Use built-in RCU list checking Date: Wed, 8 Jan 2020 01:00:39 +0530 [thread overview] Message-ID: <20200107193039.22836-1-madhuparnabhowmik04@gmail.com> (raw) From: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com> Use built-in RCU and lock checking for list_for_each_entry_rcu by passing cond argument to it. Signed-off-by: Madhuparna Bhowmik <madhuparnabhowmik04@gmail.com> --- drivers/infiniband/hw/qib/qib_verbs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/infiniband/hw/qib/qib_verbs.c b/drivers/infiniband/hw/qib/qib_verbs.c index 33778d451b82..845ba888734e 100644 --- a/drivers/infiniband/hw/qib/qib_verbs.c +++ b/drivers/infiniband/hw/qib/qib_verbs.c @@ -329,7 +329,8 @@ void qib_ib_rcv(struct qib_ctxtdata *rcd, void *rhdr, void *data, u32 tlen) if (mcast == NULL) goto drop; this_cpu_inc(ibp->pmastats->n_multicast_rcv); - list_for_each_entry_rcu(p, &mcast->qp_list, list) + list_for_each_entry_rcu(p, &mcast->qp_list, list, + lock_is_held(&(ibp->rvp.lock).dep_map)) qib_qp_rcv(rcd, hdr, 1, data, tlen, p->qp); /* * Notify rvt_multicast_detach() if it is waiting for us -- 2.17.1 _______________________________________________ Linux-kernel-mentees mailing list Linux-kernel-mentees@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next reply other threads:[~2020-01-07 19:30 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-07 19:30 madhuparnabhowmik04 [this message] 2020-01-07 19:30 ` [Linux-kernel-mentees] [PATCH 2/3] infiniband: hw: qib: qib_verbs: Use built-in RCU list checking madhuparnabhowmik04 -- strict thread matches above, loose matches on Subject: below -- 2020-01-14 16:25 madhuparnabhowmik04 2020-01-07 17:35 [PATCH 1/3] infiniband: hw: hfi1: verbs.c: " madhuparnabhowmik04 2020-01-07 17:35 ` [PATCH 2/3] infiniband: hw: qib: qib_verbs: " madhuparnabhowmik04
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=20200107193039.22836-1-madhuparnabhowmik04@gmail.com \ --to=madhuparnabhowmik04@gmail.com \ --cc=dennis.dalessandro@intel.com \ --cc=dledford@redhat.com \ --cc=frextrite@gmail.com \ --cc=joel@joelfernandes.org \ --cc=linux-kernel-mentees@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rdma@vger.kernel.org \ --cc=mike.marciniszyn@intel.com \ --cc=paulmck@kernel.org \ --cc=rcu@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: linkBe 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.