linux-kernel - Re: [x86, vdso] BUG: unable to handle kernel paging request at d34bd000

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: <1394208388.1012.2.camel@wall-e.seibold.net>
Date:	Fri, 07 Mar 2014 17:06:28 +0100
From:	Stefani Seibold <stefani@...bold.net>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [x86, vdso]  BUG: unable to handle kernel paging request at
 d34bd000

Am Freitag, den 07.03.2014, 18:21 +0800 schrieb Fengguang Wu:
> Hi Stefani,
> 
> On Fri, Mar 07, 2014 at 10:57:28AM +0100, Stefani Seibold wrote:
> > Hi Fengguang,
> > 
> > did you test the config i had sent to you?
> > 
> > My test was all done with current 3.14-rc tree. And with this i have no
> > problem. 
> 
> The regression is found on commit 4dea8e4824b363c53f320d328040d7c6c5921419
> ("x86, vdso: Add 32 bit VDSO time support for 32 bit kernel") in tip tree.
> 
> In the bisect log, you can see that next-20140306 is GOOD. So there's
> no way you can find the bug in 3.14-rcX.
> 
> > I just cloned the tip tree and i figured out that the patch was dropped
> > again (BTW: git log does not show that it was ever applied).
> 
> You can still access that specific commit:
> 
> wfg@bee /tmp% git clone --reference /c/linux git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

As i wrote i already cloned the tip tree!!!!!!

But i cannot see the changeset, there is also no VDSO changes set in the
git log.



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