From: Bin Ren <bin.ren@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Gerd Knorr <kraxel@suse.de>,
xen-devel@lists.xensource.com,
Steven Hand <Steven.Hand@cl.cam.ac.uk>
Subject: Re: bug: slab corruption (net backend?)
Date: Mon, 11 Jul 2005 15:29:10 +0100 [thread overview]
Message-ID: <8ae780250507110729777901bd@mail.gmail.com> (raw)
In-Reply-To: <a776c5dde83e89353dc30ce76e4c67a6@cl.cam.ac.uk>
Not sure whether this is related or not. Interdomain NFS stops working
with the latest xen-unstable. Haven't taken a closer look though. Last
time the same thing happened was when checksum offloading was added.
- Bin
On 7/11/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> On 11 Jul 2005, at 14:25, Gerd Knorr wrote:
>
> >> Can you disable tcp checksum offload (ethtool -K tx off) and see
> >> if you can reproduce this problem?
> >
> > Never seen that again since I've turned off CONFIG_SLAB_DEBUG,
> > which seems to be incompatible with the page mapping the xen
> > backend drivers do.
>
> Well, I'm not 100% sure of this. It looks like guard bytes aren;t
> placed around slab allocations when slab object size is near a power of
> two. But if guard header/footers are added to our skbuff data objects
> then yes: that will be broken for xen netback.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-07-11 14:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 9:41 bug: slab corruption (net backend?) Gerd Knorr
2005-07-07 10:11 ` Steven Hand
2005-07-07 11:35 ` Gerd Knorr
2005-07-07 12:05 ` Keir Fraser
2005-07-07 12:22 ` Gerd Knorr
2005-07-07 12:48 ` Gerd Knorr
2005-07-07 13:17 ` Gerd Knorr
2005-07-07 14:05 ` Keir Fraser
2005-07-07 14:18 ` Gerd Knorr
2005-07-07 14:41 ` Gerd Knorr
2005-07-07 16:06 ` Nivedita Singhvi
2005-07-11 13:25 ` Gerd Knorr
2005-07-11 13:37 ` Keir Fraser
2005-07-11 14:29 ` Bin Ren [this message]
2005-07-07 15:54 ` Gerd Knorr
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=8ae780250507110729777901bd@mail.gmail.com \
--to=bin.ren@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=bin.ren@cl.cam.ac.uk \
--cc=kraxel@suse.de \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.