From: Matt LaPlante <kernel1@cyberdogtech.com>
To: linux-kernel@vger.kernel.org
Subject: ipsec blocking issue in 2.6.25 (and earlier)
Date: Thu, 17 Apr 2008 19:33:50 -0500 [thread overview]
Message-ID: <20080417193350.8e615006.kernel1@cyberdogtech.com> (raw)
I'd like to call attention to an apparent bug that has been causing me some significant trouble lately. In brief, transmission of data over IPSEC (apparently the sendmsg call in particular) is blocking when the IPSEC connection becomes unavailable. This is causing various daemons such as named and squid to behave rather badly... in the case of named, it binds (no pun intended) up the entire daemon and it starts refusing queries from all interfaces.
I first noticed this somewhat earlier on in the 2.6.2x series, but only recently did I find a fairly comprehensive bug report with Redhat that confirmed the issue. Please see the full report here:
https://bugzilla.redhat.com/show_bug.cgi?id=427629
Please also note that I'm actually experiencing this under Ubuntu, and am using a custom built (fairly minimal; unpatched) kernel. This apparently confirms that it is not a distro-specific issue, and is most likely a fairly purvasive kernel bug.
As I can still replicate this fairly readily, I'd be glad to assist in further troubleshooting, but I'm about at the end of my range when it comes to diagnosing the issue myself.
Thanks,
Matt LaPlante
next reply other threads:[~2008-04-18 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 0:33 Matt LaPlante [this message]
2008-04-18 1:13 ` ipsec blocking issue in 2.6.25 (and earlier) David Miller
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=20080417193350.8e615006.kernel1@cyberdogtech.com \
--to=kernel1@cyberdogtech.com \
--cc=linux-kernel@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