mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Imran.Patel@nokia.com
Cc: ak@suse.de, netfilter-devel@us5.samba.org, netdev@oss.sgi.com,
	linux-kernel@vger.kernel.org
Subject: Re: skb allocation problems
Date: Tue, 10 Apr 2001 19:23:28 +0200	[thread overview]
Message-ID: <20010410192328.A21887@gruyere.muc.suse.de> (raw)
In-Reply-To: <2D6CADE9B0C6D411A27500508BB3CBD063CF0D@eseis15nok>
In-Reply-To: <2D6CADE9B0C6D411A27500508BB3CBD063CF0D@eseis15nok>; from Imran.Patel@nokia.com on Tue, Apr 10, 2001 at 07:27:29PM +0300

On Tue, Apr 10, 2001 at 07:27:29PM +0300, Imran.Patel@nokia.com wrote:
> > On Mon, Apr 09, 2001 at 07:03:46PM +0300, Imran.Patel@nokia.com wrote:
> > > I have written a test module which closely mirrors what my 
> > code tries to
> > > do(attached below). This is what i get:
> > > 
> > > PRE_R: old skb:c371ee40  new skb:c371ee30 
> > 
> > I guess oldskb->len is <=0xc, and the slab allocator packs 
> > them near together
> > in the same zone.
> 
> nope. i have checked it, the length of the older skb is perfectly ok.....and
> i even found that this weird behaviour happens only when the old skb buffer
> length is between 80 and 224 bytes. 

Well, I don't know then. You have to debug it. It's probably something stupid
(if fundamental services like alloc_skb/kfree_skb were completely buggy
someone surely would have noticed earlier)

-Andi

  reply	other threads:[~2001-04-10 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 16:27 Imran.Patel
2001-04-10 17:23 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-09 16:03 Imran.Patel
2001-04-10  6:07 ` Andi Kleen

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=20010410192328.A21887@gruyere.muc.suse.de \
    --to=ak@suse.de \
    --cc=Imran.Patel@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=netfilter-devel@us5.samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®