linux-kernel - Re: 2.6.25 crash: EIP: [<c02e2f14>] xfrm_output

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BAY103-DAV594320AC93E33D7335927B2DA0@phx.gbl>
Date:	Fri, 2 May 2008 14:26:14 +0200
From:	"Marco Berizzi" <pupilla@...mail.com>
To:	"Herbert Xu" <herbert@...dor.apana.org.au>
Cc:	<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
	<davem@...emloft.net>
Subject: Re: 2.6.25 crash: EIP: [<c02e2f14>] xfrm_output_resume+0x64/0x100 ss:esp 0068:c03a1e5c

Herbert Xu wrote:

> Marco Berizzi <pupilla@...mail.com> wrote:
>> Just few minutes ago, another 2.6.25 crash
>> with this message:
>> 
>> EIP: [<c028000a>] netif_rx+0x6a/0xd0 SS:ESP 0068:c039f868
>> 
>> http://80.204.235.230/4.jpg
> 
> OK, the xfrm_output_resume trail revealed nothing.  Combined
> with this crash however, it would appear that you've got a problem
> with live skbs being freed.  Unfortunately such problems are
> difficult to track down.
> 
> Perhaps you could enable SLAB debugging to see if we can get
> closer to the culprit?

Yes indeed, I will try next monday.

> Alternatively you could try a git bisection.

Yes, but it could take forever... :-((
As I said, I have removed the sfq and htb modules,
and I would like to wait one week to see if these
boxes will crash. I have 8 linux boxes running 2.6.25
with the same .config and only the two with htb/sfq
qdisc are crashing. Just few minutes ago I have seen
this message forwarded to netdev by David Miller:

Re: PROBLEM: kernel lockup while changing TC rules

it is talking about htb/sfq. Maybe it is related.
 
> Unless we have a way of reproducing this there isn't a lot more
> that we can do I'm afraid.

thanks anyway Herbert.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/