From: Francois Romieu <romieu@fr.zoreil.com>
To: Andreas Henriksson <andreas@fjortis.info>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Jeff Garzik <jgarzik@pobox.com>,
netdev@oss.sgi.com
Subject: Re: fealnx oopses
Date: Mon, 29 Mar 2004 01:38:34 +0200 [thread overview]
Message-ID: <20040329013834.B24996@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20040328232707.GA17524@scream.fjortis.info>; from andreas@fjortis.info on Mon, Mar 29, 2004 at 01:27:07AM +0200
Andreas Henriksson <andreas@fjortis.info> :
[...]
> > --- fealnx.c.orig Fri Nov 28 20:26:20 2003
> > +++ fealnx.c Sun Mar 28 21:32:56 2004
> > @@ -1134,15 +1134,17 @@
> > struct sk_buff *skb;
> >
> > skb = dev_alloc_skb(np->rx_buf_sz);
> > - np->lack_rxbuf->skbuff = skb;
> > -
> > if (skb == NULL)
> > break; /* Better luck next round. */
> >
>
> np->lack_rxbuf == NULL here....
>
> (verified by inserting a "BUG_ON(np->lack_rxbuf==NULL);"...)
Oops, I forgot to initialize np->lack_rxbuf correctly.
If you have some time to spend, you can change in netdev_rx:
pci_unmap_single(np->pci_dev,
np->cur_rx->buffer,
np->rx_buf_sz,
PCI_DMA_FROMDEVICE);
skb_put(skb = np->cur_rx->skbuff, pkt_len);
np->cur_rx->skbuff = NULL;
--np->really_rx_count;
into:
pci_unmap_single(np->pci_dev,
np->cur_rx->buffer,
np->rx_buf_sz,
PCI_DMA_FROMDEVICE);
skb_put(skb = np->cur_rx->skbuff, pkt_len);
np->cur_rx->skbuff = NULL;
if (!np->lack_rxbuf) <<<
np->lack_rxbuf = np->cur_rx; <<<
np->cur_rx->skbuff = NULL;
--np->really_rx_count;
It may be simpler/safer to turn (init_ring):
np->lack_rxbuf = NULL;
into
np->lack_rxbuf = np->rx_ring;
I'll check the whole thing tomorrow. It's time to sleep now.
Thanks for your report.
--
Ueimor
next prev parent reply other threads:[~2004-03-28 23:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 10:14 fealnx oopses Denis Vlasenko
2004-03-26 19:22 ` Andreas Henriksson
2004-03-26 19:33 ` [PATCH] " Jeff Garzik
2004-03-26 20:05 ` Denis Vlasenko
2004-03-27 2:13 ` Andreas Henriksson
2004-03-26 19:57 ` Denis Vlasenko
[not found] ` <40648CAF.5010203@pobox.com>
2004-03-26 22:14 ` Denis Vlasenko
2004-03-26 22:35 ` Francois Romieu
2004-03-27 0:03 ` Denis Vlasenko
2004-03-27 0:30 ` Francois Romieu
[not found] ` <4064BB35.4050301@pobox.com>
2004-03-27 21:28 ` Denis Vlasenko
2004-03-27 23:55 ` Francois Romieu
2004-03-28 20:19 ` Denis Vlasenko
2004-03-28 23:27 ` Andreas Henriksson
2004-03-28 23:38 ` Francois Romieu [this message]
2004-03-29 17:01 ` Andreas Henriksson
2004-03-29 21:49 ` Denis Vlasenko
2004-03-29 22:20 ` Francois Romieu
2004-03-29 22:50 ` Denis Vlasenko
2004-03-29 23:16 ` Denis Vlasenko
2004-03-31 21:01 ` Francois Romieu
[not found] ` <4068AC87.2030506@pobox.com>
2004-03-29 23:18 ` Denis Vlasenko
2004-03-31 16:39 ` fealnx oopses (with [PATCH]) Denis Vlasenko
2004-03-31 19:24 ` Andreas Henriksson
2004-03-31 20:38 ` Denis Vlasenko
2004-03-31 20:53 ` Jeff Garzik
2004-03-31 22:23 ` Francois Romieu
2004-04-01 11:09 ` Denis Vlasenko
2004-04-01 12:28 ` Francois Romieu
2004-03-29 7:52 ` fealnx oopses Denis Vlasenko
2004-03-26 20:20 ` Francois Romieu
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=20040329013834.B24996@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=andreas@fjortis.info \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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).