From: Michael Chan <mchan@broadcom.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <nhorman@tuxdriver.com>,
Michael Chan <mchan@broadcom.com>
Subject: [PATCH 0/3 v2] cnic fixes.
Date: Mon, 2 Jun 2014 23:08:45 -0700 [thread overview]
Message-ID: <1401775728-21043-1-git-send-email-mchan@broadcom.com> (raw)
Fix 2 sleeping function from invalid context bugs and 1 missing iscsi netlink
message bug.
v2: Fixed typo in rcu_dereference_protected() and tested with CONFIG_PROVE_RCU
Michael Chan (3):
cnic: Don't take rcu_read_lock in cnic_rcv_netevent()
cnic: Don't take cnic_dev_lock in cnic_alloc_uio_rings()
cnic: Fix missing ISCSI_KEVENT_IF_DOWN message
drivers/net/ethernet/broadcom/cnic.c | 29 ++++++++++++++++-------------
1 files changed, 16 insertions(+), 13 deletions(-)
next reply other threads:[~2014-06-03 4:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 6:08 Michael Chan [this message]
2014-06-03 6:08 ` [PATCH 1/3 v2] cnic: Don't take rcu_read_lock in cnic_rcv_netevent() Michael Chan
2014-06-03 6:08 ` [PATCH 2/3 v2] cnic: Don't take cnic_dev_lock in cnic_alloc_uio_rings() Michael Chan
2014-06-03 6:08 ` [PATCH 3/3 v2] cnic: Fix missing ISCSI_KEVENT_IF_DOWN message Michael Chan
2014-06-03 6:17 ` [PATCH 0/3 v2] cnic fixes David Miller
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=1401775728-21043-1-git-send-email-mchan@broadcom.com \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).