From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH 0/5] add printk specifier %px, unique identifier Date: Tue, 28 Nov 2017 09:41:59 -0800 Message-ID: <1511890919.19952.42.camel@perches.com> References: <1511826058-2563-1-git-send-email-me@tobin.cc> <874lpelxzh.fsf@xmission.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: "Tobin C. Harding" , "Jason A. Donenfeld" , Theodore Ts'o , Kees Cook , Paolo Bonzini , Tycho Andersen , "Roberts, William C" , Tejun Heo , Jordan Glover , Greg KH , Petr Mladek , Ian Campbell , Sergey Senozhatsky , Catalin Marinas , Will Deacon , Steven Rostedt , Chris Fries , Dave Weinstein , Daniel Micay , Djalal Harouni , "Eric W. Biederman" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Tue, 2017-11-28 at 09:33 -0800, Linus Torvalds wrote: > On Mon, Nov 27, 2017 at 10:26 PM, Eric W. Biederman > wrote: > > > > > > Oh well, I just did /proc//stack by making it just print 0 > > > unconditionally rather than the hex number. > > > > Patch? > > Oh, apparently I never pushed out yesterday. > > The patch literally just affects the (useless) hex number. So: > > cat /proc/self/stack > > now prints out > > [<0>] proc_pid_stack+0xaa/0x100 > [<0>] proc_single_show+0x48/0x80 > [<0>] seq_read+0xd2/0x410 > I considered getting rid of the whole "[<>]" thing, but that's where > "maybe there are tools that parse this" came in. > > I doubt there are any, though. If proc-ps doesn't look at this, I > don't know what could. But the format change might as well be a > separate thing if somebody cares deeply. Perhaps if there are really tools that parse this the [] should be kept the same too. >