From: Martin Costabel <costabel@wanadoo.fr>
To: Paul Mackerras <paulus@linuxcare.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.43 failed
Date: Mon, 14 Feb 2000 09:50:39 +0100 [thread overview]
Message-ID: <38A7C1DF.99A5346@wanadoo.fr> (raw)
In-Reply-To: 00021410380401.14021@argo.linuxcare.com.au
Paul Mackerras wrote:
>
> On Mon, 14 Feb 2000, Martin Costabel wrote:
[]
> > Feb 13 15:06:14 rennes-231 kernel: Warning: kfree_skb on hard IRQ
> > c7159770
> > Feb 13 15:07:24 rennes-231 last message repeated 421 times
> > Feb 13 15:12:01 rennes-231 last message repeated 97 times
> > and so on.
> >
> > How can I get rid of the warnings (short of disabling the line that
> > produces it in net/core/skbuff.c)?
>
> Find the places where dev_kfree_skb is called from interrupt context and
> change them to dev_kfree_skb_irq. If you aren't sure you can say
>
> if (in_irq())
> dev_kfree_skb_irq(skb);
> else
> dev_kfree_skb(skb);
Thanks. Your new version in 2.3.45pre works correctly (shows me once
more why I'm not a kernel developer: I replaced all 3 occurrences of
dev_kfree_skb by if (in_irq()) ... else ..., which worked, too; you
replaced just one of them by dev_kfree_skb_irq; I had tried this before,
but always got the wrong one :-( ).
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-14 8:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10002112021310.4195-100000@xpol.uchicago.edu>
2000-02-12 7:28 ` 2.3.43 failed Paul Mackerras
[not found] ` <00021211003504.00821@linux.eric.fr>
[not found] ` <38A5934B.9E259106@schweiz.org>
2000-02-12 19:53 ` Michael R. Zucca
2000-02-13 4:24 ` ramp
2000-02-13 6:23 ` Nelson Abramson
2000-02-13 7:42 ` Sucess with 2.3.44pre !! ramp
2000-02-13 7:29 ` 2.3.43 failed Paul Mackerras
2000-02-13 12:17 ` Andreas Tobler
2000-02-13 23:24 ` Paul Mackerras
2000-02-13 14:37 ` Martin Costabel
2000-02-13 23:25 ` Paul Mackerras
2000-02-14 8:50 ` Martin Costabel [this message]
2000-02-14 23:20 ` Paul Mackerras
2000-02-14 8:53 ` Eric Benard
2000-02-16 0:02 Jeremy Knope
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=38A7C1DF.99A5346@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.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).