[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140101215231.50ea361e@nehalam.linuxnetplumber.net>
Date: Wed, 1 Jan 2014 21:52:31 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: netdev@...r.kernel.org
Subject: Fw: [Bug 68011] New: spin_unlock is missed in function
(netpoll_send_skb_on_dev) in file (linux-3.12/net/core/netpoll.c)
Begin forwarded message:
Date: Wed, 1 Jan 2014 11:52:20 -0800
From: "bugzilla-daemon@...zilla.kernel.org" <bugzilla-daemon@...zilla.kernel.org>
To: "stephen@...workplumber.org" <stephen@...workplumber.org>
Subject: [Bug 68011] New: spin_unlock is missed in function (netpoll_send_skb_on_dev) in file (linux-3.12/net/core/netpoll.c)
https://bugzilla.kernel.org/show_bug.cgi?id=68011
Bug ID: 68011
Summary: spin_unlock is missed in function
(netpoll_send_skb_on_dev) in file
(linux-3.12/net/core/netpoll.c)
Product: Networking
Version: 2.5
Kernel Version: 3.12
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: shemminger@...ux-foundation.org
Reporter: atamrawi@...tate.edu
Regression: No
In function (netpoll_send_skb_on_dev) in file (linux-3.12/net/core/netpoll.c):
The structure (txq->_xmit_lock) gets successfully locked at line (383) by
(__netif_tx_trylock(txq)) and unlocked by (__netif_tx_unlock(txq)) at line
(398).
The problem occurs when the loop breaks at line (390) and the structure
(txq->_xmit_lock) still locked. In that case, the structure (txq->_xmit_lock)
never gets unlocked.
A possible solution is to call (__netif_tx_unlock(txq)) before the break at
line (390)
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists