linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Kees Cook <keescook@chromium.org>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Du Cheng <ducheng2@gmail.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Vlastimil Babka <vbabka@suse.cz>,
	William Kucharski <william.kucharski@oracle.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Nathan Chancellor <nathan@kernel.org>,
	netdev@vger.kernel.org, linux-hardening@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] niu: Add "overloaded" struct page union member
Date: Tue, 10 May 2022 00:27:53 -0700	[thread overview]
Message-ID: <YnoT+cBTNnPzzg8H@infradead.org> (raw)
In-Reply-To: <20220509222334.3544344-1-keescook@chromium.org>

On Mon, May 09, 2022 at 03:23:33PM -0700, Kees Cook wrote:
> The randstruct GCC plugin gets upset when it sees struct addresspace
> (which is randomized) being assigned to a struct page (which is not
> randomized):

Well, the right fix here is to remove this abuse from the driver, not
to legitimize it as part of a "driver" patch touching a core mm header
that doesn't even cc the mm list.

  reply	other threads:[~2022-05-10  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 22:23 [PATCH] niu: Add "overloaded" struct page union member Kees Cook
2022-05-10  7:27 ` Christoph Hellwig [this message]
2022-05-10 15:50   ` Kees Cook
2022-05-10 17:27     ` Matthew Wilcox
2022-05-10 20:20       ` Kees Cook

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=YnoT+cBTNnPzzg8H@infradead.org \
    --to=hch@infradead.org \
    --cc=arnd@arndb.de \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=davem@davemloft.net \
    --cc=ducheng2@gmail.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vbabka@suse.cz \
    --cc=william.kucharski@oracle.com \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).