From: Alexey Dobriyan <adobriyan@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 1/3] proc: randomize "struct pde_opener"
Date: Fri, 16 Feb 2018 07:48:35 +0300 [thread overview]
Message-ID: <20180216044835.GB7811@avx2> (raw)
In-Reply-To: <20180216001317.GG30522@ZenIV.linux.org.uk>
On Fri, Feb 16, 2018 at 12:13:17AM +0000, Al Viro wrote:
> On Fri, Feb 16, 2018 at 12:41:13AM +0300, Alexey Dobriyan wrote:
> > On Thu, Feb 15, 2018 at 07:07:13PM +0000, Al Viro wrote:
> > > On Wed, Feb 14, 2018 at 11:19:35AM +0300, Alexey Dobriyan wrote:
> > >
> > > > The more the merrier.
> > >
> > > ITYM "Sanity is overrated anyway."
> >
> > If you view annotations as debugging option the thing is not that bad.
>
> Yes, if your goal is to debug gcc. Look, randomize_layout is a bad idea,
> with worse implementation. It's security theatre with no real benefits,
> it makes for much harder kernel debugging, it buggers cachelines without
> noticing *AND* it triggers gcc version-dependent miscompiles that
> cheerfully cause memory corruption.
So at least gcc people should all enable it. :^)
next prev parent reply other threads:[~2018-02-16 4:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 6:30 [PATCH -mm] proc: faster open/close of files without ->release hook Alexey Dobriyan
2018-02-14 8:19 ` [PATCH -mm 1/3] proc: randomize "struct pde_opener" Alexey Dobriyan
2018-02-14 8:23 ` [PATCH -mm 2/3] proc: move "struct pde_opener" to kmem cache Alexey Dobriyan
2018-02-14 8:24 ` [PATCH -mm 3/3] proc: account "struct pde_opener" Alexey Dobriyan
2018-02-15 19:07 ` [PATCH -mm 1/3] proc: randomize " Al Viro
2018-02-15 21:41 ` Alexey Dobriyan
2018-02-16 0:13 ` Al Viro
2018-02-16 1:03 ` Kees Cook
2018-02-16 4:48 ` Alexey Dobriyan [this message]
2018-02-16 0:53 ` Kees Cook
2018-02-16 4:41 ` Alexey Dobriyan
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=20180216044835.GB7811@avx2 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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.