From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Chris Boot <bootc@bootc.net>
Cc: kernel list <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, grsecurity@grsecurity.net
Subject: Re: KERNEL: assertion (!sk->sk_forward_alloc) failed at net/* (again)
Date: Tue, 16 May 2006 14:51:21 +0400 [thread overview]
Message-ID: <20060516105121.GA18677@2ka.mipt.ru> (raw)
In-Reply-To: <16537920-30DB-4FF7-BD51-DC8517BF4321@bootc.net>
On Tue, May 16, 2006 at 11:38:38AM +0100, Chris Boot (bootc@bootc.net) wrote:
> May 16 09:15:12 baldrick kernel: [6442250.504000] KERNEL: assertion (!
> sk->sk_forward_alloc) failed at net/core/stream.c (283)
> May 16 09:15:12 baldrick kernel: [6442250.513000] KERNEL: assertion (!
> sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (150)
>
> tcp segmentation offload: on
This bug was fixed in .10 in stack and .12 in e1000 driver
(probably unrelated to your problem, if you do not have packet plit
option enabled).
> Many thanks,
> Chris
--
Evgeniy Polyakov
next prev parent reply other threads:[~2006-05-16 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 10:38 KERNEL: assertion (!sk->sk_forward_alloc) failed at net/* (again) Chris Boot
2006-05-16 10:51 ` Evgeniy Polyakov [this message]
2006-05-16 10:53 ` Chris Boot
2006-05-16 11:01 ` Ingo Oeser
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=20060516105121.GA18677@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=bootc@bootc.net \
--cc=grsecurity@grsecurity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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.