linux-kernel - Re: Oops in ring_buffer_alloc_read

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]

Date:	Sun, 23 Jun 2013 11:06:05 -0700
From:	Andi Kleen <ak@...ux.jf.intel.com>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Vaibhav Nagarnaik <vnagarnaik@...gle.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...ux.jf.intel.com>
Subject: Re: Oops in ring_buffer_alloc_read_page()

> Good question! I tried disabling CPA self-test and the BUG does not
> show up for 10000 boots. So this should be the root cause.
> 

The test is very different now than what I wrote originally, but I would
generally expect any bug to be in change_page_attr(), not be in the
self test.

> > > [   36.776024] *pde = 0e3e1067 *pte = 061e7260 

The oops is in a 2MB page that should not have changed by CPA 
in theory (it just adds 4KB pages)

I suppose you could log the addresses touched by the test and compare
to the oops addresses.

Most likely the reason you don't see it all the time is that the 
test is randomized. So you could make it more stable by fixing
the seed in pageattr-test and perhaps changing it to use more
pages.

> > > [   36.776024] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007

Could be also some virtualization problem?

-andi

-- 
ak@...ux.intel.com -- Speaking for myself only
--
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/