linux-kernel - Re: [perf] BUG: unable to handle kernel NULL pointer dereference at 00000085

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20141007081732.GF19379@twins.programming.kicks-ass.net>
Date:	Tue, 7 Oct 2014 10:17:32 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Jet Chen <jet.chen@...el.com>, Su Tao <tao.su@...el.com>,
	Yuanhan Liu <yuanhan.liu@...el.com>, LKP <lkp@...org>,
	linux-kernel@...r.kernel.org, Dave Jones <davej@...hat.com>
Subject: Re: [perf] BUG: unable to handle kernel NULL pointer dereference at
 00000085

On Tue, Oct 07, 2014 at 01:03:48PM +0800, Fengguang Wu wrote:
> > What is lacking is the actual .config.
> 
> Sorry, attached the .config. I expected the script to auto attach it,
> but obviously it's not yet perfect and failed to attach .config in
> this case.

Sure no problem, just figured I'd tell you.

> > Also the times above (~285 seconds) seem to suggest userspace needs to
> > do something ?
> 
> It's trinity. I'll try upgrade it, but it seems be valid for trinity
> to feed kernel with any parameters that it can accept -- unless the
> kernel completely rejects it one day.

OK, does it make sense to augment that script you have with a trinity
parameter? Maybe have that userspace read the kernel cmdline and also
run trinity when observed?

That way you can provide full reproduction environments, which it
appears you're striving towards.


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