From: David Miller <davem@davemloft.net>
To: ak@suse.de
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.19rc2 XFRM does too large direct mapping allocations for hashes
Date: Wed, 18 Oct 2006 12:37:47 -0700 (PDT) [thread overview]
Message-ID: <20061018.123747.59655253.davem@davemloft.net> (raw)
In-Reply-To: <200610181350.22049.ak@suse.de>
From: Andi Kleen <ak@suse.de>
Date: Wed, 18 Oct 2006 13:50:22 +0200
> I got this while restarting ipsec on a 2.6.19rc2 system that was
> up for a few days.
It's been fixed already in current GIT.
The xfrm state counters weren't being maintained correctly,
so they'd go "negative" and the hashing code thought it
needed a "huge" hash table. :-)
prev parent reply other threads:[~2006-10-18 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 11:50 2.6.19rc2 XFRM does too large direct mapping allocations for hashes Andi Kleen
2006-10-18 19:37 ` David Miller [this message]
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=20061018.123747.59655253.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--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 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).