From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752959AbdK2VOk (ORCPT ); Wed, 29 Nov 2017 16:14:40 -0500 Received: from mail-it0-f50.google.com ([209.85.214.50]:42539 "EHLO mail-it0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752607AbdK2VOj (ORCPT ); Wed, 29 Nov 2017 16:14:39 -0500 X-Google-Smtp-Source: AGs4zMbGdQnTiDWnmVTmjdBeIlB9rm1PxbEuDpUi2S3HtDwx0CpWRLe0vpA6hhfISgWLojWucmkeBRiOucAmf327jZs= MIME-Version: 1.0 In-Reply-To: <20171129210848.GF6217@eros> References: <20171129045927.GA6217@eros> <20171129210848.GF6217@eros> From: Linus Torvalds Date: Wed, 29 Nov 2017 13:14:38 -0800 X-Google-Sender-Auth: tix95rYWTJp-viFboluIijlm3XQ Message-ID: Subject: Re: [GIT PULL] hash addresses printed with %p To: "Tobin C. Harding" Cc: LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 29, 2017 at 1:08 PM, Tobin C. Harding wrote: > > If you haven't wasted enough time on this can you tell me what you mean > by 'completely breaks %pK'? The whole point of %pK is that it's a "safer" %p that doesn't leak information if you set kptr_restrict. With that patch-set, it now leaks _more_ information than %p when kptr_restrict isn't set, so %pK went from "be more careful than %p" to "be wildly less careful than %p". Not because %pK itself changed, but because the semantics of %p did. The baseline moved, and the "safe" version did not. Linus