linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Carsten Emde <C.Emde@osadl.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	John Kacur <jkacur@redhat.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	<stable-rt@vger.kernel.org>,
	Mike Gabraith <umgwanakikbuti@gmail.com>
Subject: [PATCH RT 4/9] scsi/fcoe: Fix get_cpu()/put_cpu_light() imbalance in fcoe_recv_frame()
Date: Fri, 23 Sep 2016 11:28:30 -0400	[thread overview]
Message-ID: <20160923152839.278510558@goodmis.org> (raw)
In-Reply-To: 20160923152826.308633481@goodmis.org

[-- Attachment #1: 0004-scsi-fcoe-Fix-get_cpu-put_cpu_light-imbalance-in-fco.patch --]
[-- Type: text/plain, Size: 1094 bytes --]

3.12.63-rt85-rc2 stable review patch.
If anyone has any objections, please let me know.

------------------

From: Mike Galbraith <umgwanakikbuti@gmail.com>

During master->rt merge, I stumbled across the buglet below.

Fix get_cpu()/put_cpu_light() imbalance.

Cc: stable-rt@vger.kernel.org
Signed-off-by: Mike Gabraith <umgwanakikbuti@gmail.com>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
 drivers/scsi/fcoe/fcoe.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/scsi/fcoe/fcoe.c b/drivers/scsi/fcoe/fcoe.c
index b439c20524ce..bd02c14b3719 100644
--- a/drivers/scsi/fcoe/fcoe.c
+++ b/drivers/scsi/fcoe/fcoe.c
@@ -1809,7 +1809,7 @@ static void fcoe_recv_frame(struct sk_buff *skb)
 	 */
 	hp = (struct fcoe_hdr *) skb_network_header(skb);
 
-	stats = per_cpu_ptr(lport->stats, get_cpu());
+	stats = per_cpu_ptr(lport->stats, get_cpu_light());
 	if (unlikely(FC_FCOE_DECAPS_VER(hp) != FC_FCOE_VER)) {
 		if (stats->ErrorFrames < 5)
 			printk(KERN_WARNING "fcoe: FCoE version "
-- 
2.8.1

  parent reply	other threads:[~2016-09-23 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23 15:28 [PATCH RT 0/9] Linux 3.12.63-rt85-rc2 Steven Rostedt
2016-09-23 15:28 ` [PATCH RT 1/9] timers: wakeup all timer waiters Steven Rostedt
2016-09-23 15:28 ` [PATCH RT 2/9] timers: wakeup all timer waiters without holding the base lock Steven Rostedt
2016-09-23 15:28 ` [PATCH RT 3/9] sched: lazy_preempt: avoid a warning in the !RT case Steven Rostedt
2016-09-23 15:28 ` Steven Rostedt [this message]
2016-09-23 15:28 ` [PATCH RT 5/9] net: add back the missing serialization in ip_send_unicast_reply() Steven Rostedt
2016-09-23 15:28 ` [PATCH RT 6/9] net: add a lock around icmp_sk() Steven Rostedt
2016-09-23 15:28 ` [PATCH RT 7/9] fs/dcache: resched/chill only if we make no progress Steven Rostedt
2016-09-23 15:28 ` [PATCH RT 8/9] fs/dcache: incremental fixup of the retry routine Steven Rostedt
2016-09-23 15:28 ` [PATCH RT 9/9] Linux 3.12.63-rt85-rc2 Steven Rostedt
2016-09-23 15:31 ` [PATCH RT 0/9] " Steven Rostedt

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=20160923152839.278510558@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=C.Emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=stable-rt@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=umgwanakikbuti@gmail.com \
    /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).