From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752863Ab3ABP1v (ORCPT ); Wed, 2 Jan 2013 10:27:51 -0500 Received: from mx1.redhat.com ([209.132.183.28]:30417 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752778Ab3ABP1g (ORCPT ); Wed, 2 Jan 2013 10:27:36 -0500 Date: Wed, 2 Jan 2013 10:27:27 -0500 From: Dave Jones To: Linux Kernel Cc: Ingo Molnar , Peter Zijlstra Subject: schedule_timeout: wrong timeout value fffffffffffffff0 Message-ID: <20130102152727.GA25940@redhat.com> Mail-Followup-To: Dave Jones , Linux Kernel , Ingo Molnar , Peter Zijlstra MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 This happened to a box I left running fuzz tests over the holidays. schedule_timeout: wrong timeout value fffffffffffffff0 Pid: 6606, comm: trinity-child1 Not tainted 3.8.0-rc1+ #43 Call Trace: [] schedule_timeout+0x305/0x340 [] ? preempt_schedule+0x42/0x60 [] ? _raw_spin_unlock_irqrestore+0x75/0x80 [] audit_log_start+0x311/0x470 [] ? __rcu_read_unlock+0x5c/0xa0 [] ? try_to_wake_up+0x320/0x320 [] audit_log_exit+0x4b/0xfb0 [] ? vm_mmap_pgoff+0x8b/0xb0 [] ? get_lock_stats+0x22/0x70 [] ? put_lock_stats.isra.23+0xe/0x40 [] ? lock_release_holdtime.part.24+0xcb/0x130 [] ? up_write+0x23/0x40 [] ? vm_mmap_pgoff+0x8b/0xb0 [] ? sysret_signal+0x5/0x47 [] __audit_syscall_exit+0x25f/0x2c0 [] sysret_audit+0x17/0x21