From: "D. Stussy" <spam+newsgroups@bde-arc.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: [Additional]: Kernel non-fatal(?) bug - IPsec - Holding atomic when calling scheduler.
Date: Sun, 18 Dec 2011 15:14:37 -0800 [thread overview]
Message-ID: <jcls4q$518$1@snarked.org> (raw)
In-Reply-To: i8PHj-7xK-5@gated-at.bofh.it
Even a simple policy set like this triggers the bug:
# setkey -c <<EOF
> spdadd localhost localhost any -P in none;
> spdadd localhost localhost any -P out none;
> EOF
Obviously, turning off IPsec on the loopback address is a given, yet
despite declaring "none" for the policy (as opposed to "ipsec" with a real
policy) is enough to trigger the bug.
Is anyone else experiencing this bug?
parent reply other threads:[~2011-12-18 23:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <i8PHj-7xK-5@gated-at.bofh.it>]
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='jcls4q$518$1@snarked.org' \
--to=spam+newsgroups@bde-arc.ampr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=replies+newsgroups@kd6lvw.ampr.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.