linux-kernel - Re: PROBLEM: reproducible crash KVM+nf

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] [day] [month] [year] [list]

Message-Id: <1264677660.2793.128.camel@tonnant>
Date:	Thu, 28 Jan 2010 06:21:00 -0500
From:	Jon Masters <jonathan@...masters.org>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: reproducible crash KVM+nf_conntrack all recent 2.6 
 kernels

On Thu, 2010-01-28 at 11:19 +0200, Alexey Dobriyan wrote:
> > RIP: 0010:[<ffffffff813b4115>]  [<ffffffff813b4115>] destroy_conntrack+0x82/0x114
> 
> Rebuild kernel with CONFIG_DEBUG_INFO=y.
> Double sure conntracking is compiled-in.
> Then run
> 
>     addr2line -e vmlinux $RIP
> 
> it will tell exact line where kernel is oopsing.

I posted a followup with that detail later in the thread. In every case
the kernel has CONFIG_DEBUG_INFO set, and in the latter example I posted
I had turned on almost every other debugging option. I currently have a
kernel with netfilter debugging turned on but that's proving harder to
cause to fall over (likely because I changed several other options, so I
will rebuild it to be identical to earlier with just NF debug on).

Jon.

--
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/