From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: SathyaNarayanan <sathyan@teamf1.com>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
netdev@vger.kernel.org
Subject: Re: [PATCH] ibm_newemac: Fixes kernel crashes when speed of cable connected changes
Date: Fri, 27 Jun 2008 18:54:22 +1000 [thread overview]
Message-ID: <1214556862.8011.534.camel@pasglop> (raw)
In-Reply-To: <1946a170806262354k582ad86asc9a1a8383aad45a4@mail.gmail.com>
>
> > for (i = 0; i < NUM_TX_BUFF; ++i) {
> > - if (dev->tx_skb[i]) {
> > + if (dev->tx_skb[i] &&
> dev->tx_desc[i].data_ptr) {
>
>
> Why changing the test above ?
>
> The reason for changing this condition is , In any of the case if
> the dev->tx_skb is not containing valid address, Then while clearing
> it you may be resulted in "address voilations". This additional
> condition ensures that we are clearing the valid skbs.
> Further this condition is not in general data flow, So this additional
> condition should not have any impact on performance.
Do you see -any- case where tx_skb[i] and dev->tx_desc[i].data_ptr would
be out of sync ? If that's the case, shouldn't we cleanup instead of
leaving some kind of stale entry in the ring ?
In addition, in pure theory, data_ptr == 0 is a valid DMA address :-) So
I think that part of the patch shouldn't be there.
>
> > dev_kfree_skb(dev->tx_skb[i]);
> > dev->tx_skb[i] = NULL;
> > if (dev->tx_desc[i].ctrl &
> MAL_TX_CTRL_READY)
> > @@ -2719,6 +2719,10 @@ static int __devinit
> emac_probe(struct of_device *ofdev,
> > /* Clean rings */
> > memset(dev->tx_desc, 0, NUM_TX_BUFF * sizeof(struct
> mal_descriptor));
> > memset(dev->rx_desc, 0, NUM_RX_BUFF * sizeof(struct
> mal_descriptor));
> > + for (i = 0; i <= NUM_TX_BUFF; i++)
> > + dev->tx_skb[i] = NULL;
> > + for (i = 0; i <= NUM_RX_BUFF; i++)
> > + dev->rx_skb[i] = NULL;
>
>
> Why not use memset here too ?
> Yes, It was valid to use memset here. I can send the modified
> patch for it.
Please do, thanks.
Cheers,
Ben.
prev parent reply other threads:[~2008-06-27 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 12:54 [PATCH] ibm_newemac: Fixes kernel crashes when speed of cable connected changes Stefan Roese
2008-06-23 23:20 ` Benjamin Herrenschmidt
2008-06-27 6:54 ` SathyaNarayanan
2008-06-27 8:54 ` Benjamin Herrenschmidt [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=1214556862.8011.534.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=sathyan@teamf1.com \
--cc=sr@denx.de \
/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).