* [PATCH net 0/3 v2]tg3: synchronize_irq() should be called without taking locks
@ 2015-01-14 19:33 Prashant Sreedharan
2015-01-14 22:06 ` David Miller
0 siblings, 1 reply; 2+ messages in thread
From: Prashant Sreedharan @ 2015-01-14 19:33 UTC (permalink / raw)
To: davem; +Cc: netdev, mchan, peter, Prashant Sreedharan
v2: Added Reported-by, Tested-by fields and reference to the thread that
reported the problem
This series addresses the problem reported by Peter Hurley in mail thread
https://lkml.org/lkml/2015/1/12/1082
Prashant Sreedharan (3):
tg3_timer() should grab tp->lock before checking for tp->irq_sync
tg3_reset_task() needs to use rtnl_lock to synchronize
Release tp->lock before invoking synchronize_irq()
Our QA team also has validated this patch series. Thanks.
drivers/net/ethernet/broadcom/tg3.c | 23 ++++++++++++++++++++---
1 files changed, 20 insertions(+), 3 deletions(-)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH net 0/3 v2]tg3: synchronize_irq() should be called without taking locks
2015-01-14 19:33 [PATCH net 0/3 v2]tg3: synchronize_irq() should be called without taking locks Prashant Sreedharan
@ 2015-01-14 22:06 ` David Miller
0 siblings, 0 replies; 2+ messages in thread
From: David Miller @ 2015-01-14 22:06 UTC (permalink / raw)
To: prashant; +Cc: netdev, mchan, peter
From: Prashant Sreedharan <prashant@broadcom.com>
Date: Wed, 14 Jan 2015 11:33:12 -0800
> v2: Added Reported-by, Tested-by fields and reference to the thread that
> reported the problem
>
> This series addresses the problem reported by Peter Hurley in mail thread
> https://lkml.org/lkml/2015/1/12/1082
Series applied, thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-01-14 22:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-14 19:33 [PATCH net 0/3 v2]tg3: synchronize_irq() should be called without taking locks Prashant Sreedharan
2015-01-14 22:06 ` David Miller
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).