From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752450AbdC0QL5 (ORCPT <rfc822;w@1wt.eu>);
        Mon, 27 Mar 2017 12:11:57 -0400
Received: from mail.kernel.org ([198.145.29.136]:52850 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751124AbdC0QLu (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 27 Mar 2017 12:11:50 -0400
Date: Mon, 27 Mar 2017 12:11:11 -0400
From: Steven Rostedt <rostedt@goodmis.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>, Len Brown <lenb@kernel.org>,
        ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        "the arch/x86 maintainers" <x86@kernel.org>,
        Borislav Petkov <bp@alien8.de>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe
Message-ID: <20170327121111.242bc7b4@gandalf.local.home>
In-Reply-To: <CAK8P3a1-Fpkg-d0k9HryqW4ULVfZPL6_McLxoFbUT6CTmMoMFg@mail.gmail.com>
References: <6559f36c6c6cdc2552b0bccf31de967367aa790d.1489672478.git.jpoimboe@redhat.com>
        <20170324181254.gouyrbmppukrrbb6@treble>
        <20170324144114.16a37d47@gandalf.local.home>
        <5766300.HtmE7iLEgV@aspire.rjw.lan>
        <20170327140843.fx5y32rnc3mqiyke@treble>
        <CAK8P3a2Tm0qFiMx7VgK8bprncCCJ_w0ePrqPU3ex4LVm4fceaw@mail.gmail.com>
        <20170327113028.7f74c9b8@gandalf.local.home>
        <CAK8P3a1-Fpkg-d0k9HryqW4ULVfZPL6_McLxoFbUT6CTmMoMFg@mail.gmail.com>
X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, 27 Mar 2017 17:35:13 +0200
Arnd Bergmann <arnd@arndb.de> wrote:

> On Mon, Mar 27, 2017 at 5:30 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > On Mon, 27 Mar 2017 16:53:09 +0200  
> >> We could probably introduce a %pts format string for timespec64
> >> and have that pretty-printed.  
> >
> > Hmm, probably don't want a %p as that suggests its a pointer, which it
> > should not be. Unless we pass in the address of the number.  
> 
> The special format strings that the kernel defines all start with %p and
> require passing by reference so we don't get a warning from gcc. We can't
> just make up new format strings otherwise, but we can create new meaning
> for special pointers as we do for struct resource and others.
> 

That's fine, but we need to be careful when it comes to tracing.
Passing in the address of a structure in the ring buffer may be fine,
but we need to make sure that an address pointing to something other
than the ring buffer is forbidden.

I'll need to update libtraceevent to handle such cases too.

-- Steve