From: David Laight <David.Laight@ACULAB.COM>
To: 'Linus Torvalds' <torvalds@linux-foundation.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Ilya Dryomov <idryomov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Petr Mladek <pmladek@suse.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Randy Dunlap <rdunlap@infradead.org>,
Kees Cook <keescook@chromium.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
"Tobin C . Harding" <me@tobin.cc>
Subject: RE: [PATCH v2] vsprintf: don't obfuscate NULL and error pointers
Date: Fri, 10 Apr 2020 09:40:01 +0000 [thread overview]
Message-ID: <0fd21b6115b647baac23ee926b4c76f8@AcuMS.aculab.com> (raw)
In-Reply-To: <CAHk-=wgndVg4U2rh_6e8YBuhN+78wEiyTuCRTqfWuSZzGC6f_w@mail.gmail.com>
From: Linus Torvalds
> Sent: 08 April 2020 17:23
> On Wed, Apr 8, 2020 at 8:08 AM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> >
> > For the better understanding the current state of affairs I suggest to respin
> > new version after rc1 and we will see again.
If the hash of a pointer ends up being one of the values that
wouldn't be hashed, perhaps it should be hashed again.
That will remove any possible confusion.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-04-10 9:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 17:12 Ilya Dryomov
2020-02-19 17:37 ` Andy Shevchenko
2020-02-19 18:07 ` Ilya Dryomov
2020-02-19 19:23 ` Ilya Dryomov
2020-04-07 21:45 ` Ilya Dryomov
2020-04-07 22:31 ` Andy Shevchenko
2020-04-08 14:38 ` Ilya Dryomov
2020-04-08 15:06 ` Andy Shevchenko
2020-04-08 15:52 ` Ilya Dryomov
2020-04-08 16:23 ` Linus Torvalds
2020-04-10 9:40 ` David Laight [this message]
2020-04-13 9:24 ` Ilya Dryomov
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=0fd21b6115b647baac23ee926b4c76f8@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=andy.shevchenko@gmail.com \
--cc=idryomov@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=me@tobin.cc \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®