Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752980AbaAXVBc (ORCPT ); Fri, 24 Jan 2014 16:01:32 -0500 Received: from mx1.redhat.com ([209.132.183.28]:20296 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752463AbaAXVB2 (ORCPT ); Fri, 24 Jan 2014 16:01:28 -0500 Date: Fri, 24 Jan 2014 16:00:52 -0500 From: Dave Jones To: Tommi Rantala Cc: Ingo Molnar , Peter Zijlstra , trinity@vger.kernel.org, LKML Subject: Re: sched_rr_get_interval NULL pointer OOPS Message-ID: <20140124210052.GB6838@redhat.com> Mail-Followup-To: Dave Jones , Tommi Rantala , Ingo Molnar , Peter Zijlstra , trinity@vger.kernel.org, LKML References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/