From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: yoseph.basri@gmail.com, bb@kernelpanic.ru,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
Date: Wed, 8 Feb 2006 18:10:21 -0800 [thread overview]
Message-ID: <4807377b0602081810l55e4cbdfyeb9102bd50d04641@mail.gmail.com> (raw)
In-Reply-To: <20060208.141205.129707967.davem@davemloft.net>
On 2/8/06, David S. Miller <davem@davemloft.net> wrote:
> From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
> Date: Wed, 8 Feb 2006 12:07:14 -0800
>
> > this should be on netdev (cc'd), i included some of the thread here.
> ...
> > I though Herbert had fixed these, and it looks like half the patches
> > got into 2.6.14.3, but not the fix to the fix committed on 9-6 (not in
> > 2.6.14.* at all)
>
> What are the changeset IDs so I can fix this?
I think the commit id that is missing from 2.6.14.X is
fb5f5e6e0cebd574be737334671d1aa8f170d5f3
but here is the web link if i gave the wrong info
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fb5f5e6e0cebd574be737334671d1aa8f170d5f3
next prev parent reply other threads:[~2006-02-09 2:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 9:46 Yoseph Basri
2006-02-07 10:32 ` Boris B. Zhmurov
2006-02-08 3:02 ` Yoseph Basri
2006-02-08 20:07 ` Jesse Brandeburg
2006-02-08 22:12 ` David S. Miller
2006-02-09 2:10 ` Jesse Brandeburg [this message]
2006-03-10 10:59 ` David S. Miller
2006-02-09 19:17 ` Boris B. Zhmurov
2006-02-09 19:25 ` Ian McDonald
2006-02-09 19:32 ` Boris B. Zhmurov
2006-02-09 19:37 ` Ian McDonald
2006-03-10 10:59 ` David S. Miller
2006-03-10 15:51 ` Krzysztof Oledzki
2006-03-12 10:30 ` Michal Feix
2006-02-16 21:02 ` Jan-Frode Myklebust
-- strict thread matches above, loose matches on Subject: below --
2006-03-03 6:12 Johan Lundgren
2005-11-28 12:36 Mark Nipper
2005-11-28 13:44 ` Miquel van Smoorenburg
2005-11-28 16:44 ` Jesse Brandeburg
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=4807377b0602081810l55e4cbdfyeb9102bd50d04641@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=bb@kernelpanic.ru \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoseph.basri@gmail.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 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®