Re: Oops with kernel 2.4.22 and IPSEC backport from 01.09

[Nuno Ferreira (nuno.ferreira@graycell.biz)]

On Sat, 2003-09-13 at 22:55, Herbert Xu wrote:
> On Sat, Sep 13, 2003 at 04:00:52PM +0100, Nuno Ferreira wrote:
> > 
> > Last night the call the BUG you changed the condition for in your patch
> > was triggered, but I can't tell you any more than that because there is
> > nothing in the log files and the person that rebooted the machine only
> > wrote the first line of the console output.
> > Do you want me to write it down the next time it happens?
> 
> Yes I need the stack trace.

Well, the problem happened again with a new client, maybe it's caused by
some misconfiguration on the client side.

I had to write the oops by hand so if you need anything else just ask.
The oops is on xfrm_policy.c, line 238
235:void __xfrm_policy_destroy(struct xfrm_policy *policy)
236:{
237:       if (policy->dead < 2)
238:                BUG();
Just to remind you, this is with the 2.4.22, the ipsec back port from
2003-09-07 and the debugging patch that you sent in a previous email.

Here's the call trace:
Adhoc c02297fc <xfrm_policy_timer+1f0/1fc>
Adhoc c022960c <xfrm_policy_timer+0/1fc>
Adhoc c01dc9c0 <rh_int_timer_do+0/44>
Adhoc c0111270 <process_timeout+0/48>
Adhoc c011a8cc <timer_bh+24c/368>
Adhoc c0117a22 <bh_action+1a/40>
Adhoc c0117966 <tasklet_hi_action+4a/70>
Adhoc c011778a <do_softirq+5a/a4>
Adhoc c0108022 <do_IRQ+96/a8>
Adhoc c0105220 <default_idle+0/28>
Adhoc c0105220 <default_idle+0/28>
Adhoc c010a128 <call_do_IRQ+5/d>
Adhoc c0105220 <default_idle+0/28>
Adhoc c0105220 <default_idle+0/28>
Adhoc c0105243 <default_idle+23/28>
Adhoc c01052a9 <cpu_idle+41/54>
Adhoc c0105000 <_stext+0/0>
Adhoc c0105027 <rest_init+27/28>

--
Nuno

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html