From owner-freebsd-threads@FreeBSD.ORG  Thu Nov 27 21:17:01 2014
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0087EA42
 for <freebsd-threads@FreeBSD.org>; Thu, 27 Nov 2014 21:17:00 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id DCCE8E67
 for <freebsd-threads@FreeBSD.org>; Thu, 27 Nov 2014 21:17:00 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sARLH0f9083960
 for <freebsd-threads@FreeBSD.org>; Thu, 27 Nov 2014 21:17:00 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 193367] [panic] sleeping thread
Date: Thu, 27 Nov 2014 21:17:00 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 9.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: rea@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-193367-16-jN1ZxYKsFd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-193367-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-193367-16@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads/>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Nov 2014 21:17:01 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193367

Eygene Ryabinkin <rea@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rea@FreeBSD.org

--- Comment #8 from Eygene Ryabinkin <rea@FreeBSD.org> ---
Looks like there is at least off-by-one access to the driver-specific ioctl
array, http://codelabs.ru/fbsd/patches/drm2/fix-drm_drv-off-by-one.diff, since
max_ioctl is not a number of a highest supported ioctl number, but rather a
size of driver's ioctl array.

-- 
You are receiving this mail because:
You are the assignee for the bug.