From owner-freebsd-current@FreeBSD.ORG Sun Jul 5 08:17:19 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B228B1065673; Sun, 5 Jul 2009 08:17:19 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3028FC13; Sun, 5 Jul 2009 08:17:19 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:35339 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.69) (envelope-from ) id 1MNMuC-0000OC-3k; Sun, 05 Jul 2009 10:17:01 +0200 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id D82BA3E0D; Sun, 5 Jul 2009 10:16:56 +0200 (CEST) Message-Id: <31D779DF-EFD0-4255-9177-0F88CA7067CC@exscape.org> From: Thomas Backman To: bug-followup@FreeBSD.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sun, 5 Jul 2009 10:16:54 +0200 X-Mailer: Apple Mail (2.935.3) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1MNMuC-0000OC-3k. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1MNMuC-0000OC-3k 9805ad6bd6ac4f177c89082cb12f064c Cc: FreeBSD current , re@freebsd.org Subject: Re: kern/127441: [dtrace] Dtrace timestamp variable is wrapping as if define as uint32_t X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jul 2009 08:17:19 -0000 Could we have this patch merged in time for 8.0? I don't know if the problems in the PR followups are big enough, but considering that the current implementation is horribly broken for everyone, and the patch fixes it for a large number of people, I don't really see the downside in merging it for the time being. Regards, Thomas