From: Alex A <alecsnox@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Frag is bigger than frame.
Date: Mon, 10 Jun 2013 22:15:54 -0700 [thread overview]
Message-ID: <CAA9v1NhBSQYnevxhsv8_w6cid1cnuNBggDGy=nzUfuJyHS9v7A@mail.gmail.com> (raw)
In-Reply-To: <20130604200807.GA7688@zion.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2462 bytes --]
On Tue, Jun 4, 2013 at 1:08 PM, Wei Liu <wei.liu2@citrix.com> wrote:
> On Tue, Jun 04, 2013 at 12:56:35PM -0700, Alex A wrote:
> [...]
> > > >
> > > > we just hit this bug as well on CentOS 5.9 with kernels
> > > > 2.6.18-348.4.1.el5 and 2.6.18-348.6.1.el5, however I checked it on
> all
> > > > domUs and dom0s GSO is off, only TSO is on. Would TSO still cause
> this
> > > > issue?
> > > >
> > >
> > > I really think the proper thing to do is to fix your backend instead of
> > > working around that problem -- the patch is available now and you're
> > > running your customized kernel, right?
> > >
> > >
> > > Wei.
> > >
> > > > Alex
> > >
> >
> >
> > I completely agree that fixing the backend is the proper thing to do. Do
> > you mean these patches?
> >
> >
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=697089dc13c52d668322ac6cb8548520de27ed0e
> >
> >
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=9ecd1a75d977e2e8c48139c7d3efed183f898d94
> >
> >
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=2810e5b9a7731ca5fce22bfbe12c96e16ac44b6f
> >
> >
> http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=03393fd5cc2b6cdeec32b704ecba64dbb0feae3c
> >
> >
> > If I'm not mistaken aren't these patches against 2.6.3x kernel or 3.0.x?
> > I'm running 2.6.18, so I would have to port those patches to 2.6.18 base,
> > unless there exist same patches for 2.6.18?
> > Also you are correct, we are running our custom compiled rhel kernels,
> that
> > are based on rhel source rpms.
> >
>
> Sorry I don't understand. Do you mean your Dom0 is 2.6.18? My patches
> are against 3.10, the backporting is undergoing, however I don't think
> they will be backported to 2.6.18. If you're running 2.6.18 Dom0,
> presumably who backported XSA-39 will also backport those patches?
>
> Jan maintains 2.6.18 tree with minimum required patches applied to fix
> your problem (Frag bigger than frame), you might want to have a look at
> the last two patches in tree.
> http://xenbits.xen.org/hg/linux-2.6.18-xen.hg/
>
>
> Wei.
>
> > Alex
>
Yes, my Dom0 is 2.6.18, it's based on RHEL 5. They're the ones you
backported XSA-39, but they're not indicating when they will backport your
fix, they've made the bug private.
I looked at Jan's tree and found those two patches you mentioned, I will
create my own patch based on those two and rebuild the kernels.
Thank you!
Alex
[-- Attachment #1.2: Type: text/html, Size: 4086 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-06-11 5:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 0:49 Frag is bigger than frame Alex A
2013-06-04 8:44 ` Wei Liu
2013-06-04 19:56 ` Alex A
2013-06-04 20:08 ` Wei Liu
2013-06-11 5:15 ` Alex A [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-25 11:24 Steven Haigh
2013-04-25 15:11 ` Wei Liu
2013-04-25 15:36 ` Wei Liu
2013-04-26 4:21 ` Steven Haigh
2013-04-26 8:21 ` Teck Choon Giam
2013-04-26 8:36 ` Wei Liu
2013-04-26 9:13 ` Teck Choon Giam
2013-04-26 8:32 ` Wei Liu
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='CAA9v1NhBSQYnevxhsv8_w6cid1cnuNBggDGy=nzUfuJyHS9v7A@mail.gmail.com' \
--to=alecsnox@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).