From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: "prasanna.panchamukhi@riverbed.com" <prasanna.panchamukhi@riverbed.com>
Cc: "Allan, Bruce W" <bruce.w.allan@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Pieper, Jeffrey E" <jeffrey.e.pieper@intel.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] e1000: fix race condition while driver unload/reset using kref count
Date: Wed, 02 Mar 2011 17:56:41 -0800 [thread overview]
Message-ID: <1299117401.2781.6.camel@jtkirshe-MOBL1> (raw)
In-Reply-To: <1299091597-28409-1-git-send-email-prasanna.panchamukhi@riverbed.com>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Wed, 2011-03-02 at 10:46 -0800, prasanna.panchamukhi@riverbed.com
wrote:
> This race conditions occurs with reentrant e1000_down(), which gets
> called by multiple threads while driver unload or reset.
> This patch fixes the race condition when one thread tries to destroy
> the memory allocated for tx buffer_info, while another thread still
> happen to access tx buffer_info.
> This patch fixes the above race condition using kref count.
>
> Signed-off-by: Prasanna S. Panchamukhi
> <prasanna.panchamukhi@riverbed.com>
> ---
> drivers/net/e1000/e1000.h | 2 +
> drivers/net/e1000/e1000_main.c | 41
> +++++++++++++++++++++++++++++++++++++--
> 2 files changed, 40 insertions(+), 3 deletions(-)
Thanks Prasanna! I have added the patch to my e1000 queue of patches.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-03-03 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 18:46 [PATCH] e1000: fix race condition while driver unload/reset using kref count prasanna.panchamukhi
2011-03-02 22:50 ` Brandeburg, Jesse
2011-03-02 23:56 ` Prasanna Panchamukhi
2011-03-03 1:47 ` Prasanna Panchamukhi
2011-03-03 1:56 ` Jeff Kirsher [this message]
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=1299117401.2781.6.camel@jtkirshe-MOBL1 \
--to=jeffrey.t.kirsher@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.e.pieper@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=prasanna.panchamukhi@riverbed.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).