From: Ludo Stellingwerff <ludo@protactive.nl>
To: linux-kernel@vger.kernel.org
Subject: Sporadic hitting the BUG() in the XFRM Garbage Collector
Date: Tue, 07 Sep 2004 17:19:26 +0200 [thread overview]
Message-ID: <413DD17E.3050804@protactive.nl> (raw)
Hi,
One of our client's machines sometimes hits the BUG() in xfrm_state.c
(line 54).
This seems to happen at the removal of a IPsec policy. Some data: kernel
2.6.6. with Netfilter POM IPSEC-patches, ipsec-tools 0.2.3.
If I read the code correctly this would mean that the garbage collector
tries to stop an earlier deactivated timer. (del_timer returning '0')
Does anybody know what causes this? And, is a kernel BUG not a bit too
drastic for this error condition? Wouln't a WARN_ON suffice?
Thanks in advance,
Greetings,
Ludo Stellingwerff.
PS. As I'm currently not subscribed please CC me directly.
--
Ludo Stellingwerff
V&S B.V. The Netherlands
ProTactive firewall solution.
Tel: +31 172 416116
Fax: +31 172 416124
site: www.protactive.nl
demo: http://www.protactive.nl:81/netview.html
next reply other threads:[~2004-09-07 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 15:19 Ludo Stellingwerff [this message]
2004-09-07 15:37 ` Sporadic hitting the BUG() in the XFRM Garbage Collector David S. 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=413DD17E.3050804@protactive.nl \
--to=ludo@protactive.nl \
--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