linux-kernel - Re: perf: fuzzer induced mutex_lock

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:	Mon, 19 May 2014 16:48:51 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: perf: fuzzer induced mutex_lock_nested BUG

On Mon, May 19, 2014 at 10:37:11AM -0400, Vince Weaver wrote:
> 
> When sorting through the logs of the weekend's fuzzing I found a bunch of 
> these errors which apparently were not fatal.
> 
> This is a Haswell machine running 3.15-rc5 plus a number of PeterZ 
> patches, so sorry if the results are meaningless due to the extra patches.  
> I was hoping some of the fixes would show up in the mainline at some 
> point, running latest -git is enough of a pain, I don't really have the 
> cycles to be running -next or -tip kernels.
> 
> If you look up the faulting IP it's actually happening at this line in
> lockdep.c __lock_acquire()
> 
> 	if (subclass < NR_LOCKDEP_CACHING_CLASSES)
> 		class = lock->class_cache[subclass];
> 

Yeah, that's a popular place to crash if you feed it garbage. Nothing
lockdep can do about that.

> [ 3884.569315] BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8

> [ 4014.688350]  [<ffffffff810b15be>] lock_acquire+0x9e/0x120
> [ 4014.688353]  [<ffffffff8164f7e0>] mutex_lock_nested+0x50/0x360
> [ 4014.688357]  [<ffffffff8113b62c>] perf_event_init_context+0x8c/0x250
> [ 4014.688358]  [<ffffffff8113b85d>] perf_event_init_task+0x6d/0x70
> [ 4014.688359]  [<ffffffff81062165>] copy_process.part.23+0x6b5/0x1c60
> [ 4014.688362]  [<ffffffff810638e5>] do_fork+0xd5/0x330
> [ 4014.688366]  [<ffffffff81063bc6>] SyS_clone+0x16/0x20
> [ 4014.688367]  [<ffffffff8165b999>] stub_clone+0x69/0x90

Cute, I had not seen that one yet...
--
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/