All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kees Cook <keescook@chromium.org>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Christoph Hellwig <hch@lst.de>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] usercopy: Disable CONFIG_HARDENED_USERCOPY_PAGESPAN
Date: Fri, 25 Mar 2022 06:31:08 +0100	[thread overview]
Message-ID: <20220325053108.GB5204@lst.de> (raw)
In-Reply-To: <20220324230255.1362706-1-keescook@chromium.org>

On Thu, Mar 24, 2022 at 04:02:55PM -0700, Kees Cook wrote:
> CONFIG_HARDENED_USERCOPY_PAGESPAN has been mostly broken for a while,
> and it has become hard to ignore with some recent scsi changes[1].
> While there is a more complete series to replace it with better checks[2],
> it should have more soak time in -next. Instead, disable the config now,
> with the expectation that it will be fully replaced in the next kernel
> release.
> 
> [1] https://lore.kernel.org/lkml/20220324064846.GA12961@lst.de/
> [2] https://lore.kernel.org/linux-hardening/20220110231530.665970-1-willy@infradead.org/
> 
> Suggested-by: Christoph Hellwig <hch@lst.de>
> Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
> Signed-off-by: Kees Cook <keescook@chromium.org>

I'd prefer to just remove the code, but this is better than nothing:

Acked-by: Christoph Hellwig <hch@lst.de>

      reply	other threads:[~2022-03-25  5:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 23:02 [PATCH] usercopy: Disable CONFIG_HARDENED_USERCOPY_PAGESPAN Kees Cook
2022-03-25  5:31 ` Christoph Hellwig [this message]

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=20220325053108.GB5204@lst.de \
    --to=hch@lst.de \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.