All of lore.kernel.org
 help / color / mirror / Atom feed
From: Divy Le Ray <divy@chelsio.com>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: cxgb3 - fix race in EEH
Date: Wed, 08 Oct 2008 16:10:53 -0700	[thread overview]
Message-ID: <48ED3DFD.2010204@chelsio.com> (raw)
In-Reply-To: <20081008.155850.182279915.davem@davemloft.net>

David Miller wrote:
> I've applied this patch to net-next-2.6, BUT...
>
> You should show some signs of life and address the things
> Andrew Morton asked you about when you posted this patch.
>
> His questions and comments are included for your reference:
>
> ----------------------------------------
> It's deeply weird that t3_reset_qset() does
>
> 	memset(&q->tx_reclaim_timer, 0, sizeof(q->tx_reclaim_timer));
>
> There are lots of things in the timer_list which the driver has no
> business modifying.  For example, this might break the metadata in
> Thomas's debugobjects stuff, which attempts to catch things being done
> in the wrong order (I don't think it will, but still...).
>
> Rerunning init_timer() should repair the damage, but I suspect a simple
>
> 	q->tx_reclaim_timer.function = NULL;	/* explanation goes here */
>
> would suffice here.
>
>
> t3_sge_alloc_qset() could use the newer setup_timer().
> ----------------------------------------
>   

Hi Dave,

I've got a series of patches almost ready to go against net-next-2.6 - 
hopefully within the next hour, and it includes a fix for this.
I was hoping to push the patches earlier this week, thus replying to 
Andrew's concerns. It's obviously taking longer than expected to get 
these patches out. I should have answered Andrew nonetheless.
The patch series will integrate Andrew'suggestions.

Cheers,
Divy


  reply	other threads:[~2008-10-08 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 22:58 cxgb3 - fix race in EEH David Miller
2008-10-08 23:10 ` Divy Le Ray [this message]
2008-10-08 23:13   ` 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=48ED3DFD.2010204@chelsio.com \
    --to=divy@chelsio.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.