linux-kernel - Re: sched_rr_get_interval NULL pointer OOPS

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: <20140124210052.GB6838@redhat.com>
Date:	Fri, 24 Jan 2014 16:00:52 -0500
From:	Dave Jones <davej@...hat.com>
To:	Tommi Rantala <tt.rantala@...il.com>
Cc:	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>, trinity@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: sched_rr_get_interval NULL pointer OOPS

On Fri, Jan 24, 2014 at 10:55:56PM +0200, Tommi Rantala wrote:
 > Hello,
 > 
 > Trinity triggered the following bug in two separate qemu virtual
 > machines after fuzzing v3.13-3995-g0dc3fd0 for a day or two. I have
 > not been running Trinity in a while, so no idea if this is a
 > regression or not.
 
Probably been there a while. I noticed on Tuesday that I hadn't annotated
the 'policy' argument to sched_setscheduler().  Now that it's passing sensible
arguments, I'm not surprised there's some fallout if subsequent syscalls
call misc scheduler functions.

	Dave

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