All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: sergey.senozhatsky.work@gmail.com, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: [PATCH V11 4/5] vsprintf: add printk specifier %px
Date: Sun, 17 Dec 2017 07:26:45 +1100	[thread overview]
Message-ID: <20171216202645.GM2191@eros> (raw)
In-Reply-To: <20171206041924.GA2959@avx2>

On Wed, Dec 06, 2017 at 07:19:24AM +0300, Alexey Dobriyan wrote:
> > more %p grepping [filtering out all `%ps %pf %pb' variants] gives
> > a huge number of print outs that potentially can be broken now
> 
> Because people who introduce this stupid %p hashing can't be bothered
> to actually audit users:

lol, by 'stupid' he meant you Linus

	Tobin

  parent reply	other threads:[~2017-12-16 20:26 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  4:19 [PATCH V11 4/5] vsprintf: add printk specifier %px Alexey Dobriyan
2017-12-06  4:40 ` Linus Torvalds
2017-12-16 20:26 ` Tobin C. Harding [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-29  2:05 [kernel-hardening] [PATCH V11 0/5] hash addresses printed with %p Tobin C. Harding
2017-11-29  2:05 ` [PATCH V11 4/5] vsprintf: add printk specifier %px Tobin C. Harding
2017-11-29  2:05   ` Tobin C. Harding
2017-11-29  2:29   ` Linus Torvalds
2017-11-29  2:29     ` Linus Torvalds
2017-11-29  4:29     ` Tobin C. Harding
2017-11-29  4:29       ` Tobin C. Harding
2017-11-29 10:07     ` David Laight
2017-11-29 10:07       ` David Laight
2017-11-29 22:28       ` Kees Cook
2017-11-29 22:28         ` Kees Cook
2017-11-29 22:36         ` Roberts, William C
2017-11-29 22:36           ` Roberts, William C
2017-11-29 22:47         ` Linus Torvalds
2017-11-29 22:47           ` Linus Torvalds
2017-11-30 10:38         ` David Laight
2017-11-30 10:38           ` David Laight
2017-12-05 21:08           ` Randy Dunlap
2017-12-05 21:08             ` Randy Dunlap
2017-12-05 21:22             ` Linus Torvalds
2017-12-05 21:22               ` Linus Torvalds
2017-12-06  1:36               ` Sergey Senozhatsky
2017-12-06  1:36                 ` Sergey Senozhatsky
2017-12-06  1:59                 ` Linus Torvalds
2017-12-06  1:59                   ` Linus Torvalds
2017-12-06  2:15                   ` Sergey Senozhatsky
2017-12-06  2:15                     ` Sergey Senozhatsky
2017-12-06  8:32                   ` Geert Uytterhoeven
2017-12-06  8:32                     ` Geert Uytterhoeven
2017-12-06  8:45                     ` Sergey Senozhatsky
2017-12-06  8:45                       ` Sergey Senozhatsky
2017-12-07  5:17                       ` Tobin C. Harding
2017-12-07  5:17                         ` Tobin C. Harding
2017-12-07  5:29                         ` Linus Torvalds
2017-12-07  5:37                         ` Sergey Senozhatsky
2017-12-07  5:37                           ` Sergey Senozhatsky
2017-12-07  5:12                     ` Tobin C. Harding
2017-12-07  5:12                       ` Tobin C. Harding
2017-11-29 23:20   ` Andrew Morton
2017-11-29 23:20     ` Andrew Morton
2017-11-29 23:26     ` Tobin C. Harding
2017-11-29 23:26       ` Tobin C. Harding
2017-11-30  3:58       ` Joe Perches
2017-11-30  3:58         ` Joe Perches
2017-11-30  4:18         ` Tobin C. Harding
2017-11-30  4:18           ` Tobin C. Harding
2017-11-30  4:41           ` Joe Perches
2017-11-30  4:41             ` Joe Perches
2017-11-30  5:00             ` Tobin C. Harding
2017-11-30  5:00               ` Tobin C. Harding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171216202645.GM2191@eros \
    --to=me@tobin.cc \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.