netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Graham Gower <graham.gower@gmail.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Roger While <simrw@sim-basis.de>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] [TRIVIAL] prism54/islpci_eth.c: dev_kfree_skb in irq context
Date: Wed, 4 Jan 2006 09:33:27 +1030	[thread overview]
Message-ID: <6ec4247d0601031503k2232c472o@mail.gmail.com> (raw)
In-Reply-To: <43BA7810.6010308@trash.net>

On 03/01/06, Patrick McHardy <kaber@trash.net> wrote:
> Graham Gower wrote:
> > My logs were starting to fill with messages exatcly like that mentioned here:
> > http://patchwork.netfilter.org/netfilter-devel/patch.pl?id=2840
> >
> > In any event, the patch at the end of that link was never applied (it doesn't
> > fix the other call to dev_kfree_skb). After applying my patch, I've not had any
> > more messages in the logs.
>
> The patch has been applied to 2.6.15-rc. Only the first hunk of your
> patch is still required, but it doesn't apply anymore. Can you send
> a new patch against 2.6.15 please?
>

Ok, here's a new one. Hope I got it right this time.

Signed-off-by: Graham Gower <graham.gower@gmail.com>

--- linux-2.6.15/drivers/net/wireless/prism54/islpci_eth.c.orig
+++ linux-2.6.15/drivers/net/wireless/prism54/islpci_eth.c
@@ -177,7 +177,7 @@
 #endif

 			newskb->dev = skb->dev;
-			dev_kfree_skb(skb);
+			dev_kfree_skb_irq(skb);
 			skb = newskb;
 		}
 	}

      reply	other threads:[~2006-01-03 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6.1.1.1.2.20060103105620.02c523e0@192.168.6.12>
2006-01-03 12:19 ` [PATCH] [TRIVIAL] prism54/islpci_eth.c: dev_kfree_skb in irq context Graham Gower
2006-01-03 13:11   ` Patrick McHardy
2006-01-03 23:03     ` Graham Gower [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=6ec4247d0601031503k2232c472o@mail.gmail.com \
    --to=graham.gower@gmail.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=simrw@sim-basis.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).