From: Kees Cook <keescook@chromium.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Brian Foster <bfoster@redhat.com>,
kernel test robot <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org, linux-bcachefs@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [linux-next:master] BUILD REGRESSION df964ce9ef9fea10cf131bf6bad8658fde7956f6
Date: Sun, 1 Oct 2023 21:52:22 -0700 [thread overview]
Message-ID: <202310012150.72AAB06FAD@keescook> (raw)
In-Reply-To: <20231002032239.t7ghpigbq5jy3ng7@moria.home.lan>
On Sun, Oct 01, 2023 at 11:22:39PM -0400, Kent Overstreet wrote:
> I'm not leaping at the chance to reorganize my fundamental data
> structures for this.
Yeah, understood. Thanks for taking a look at it!
> Can we get such an escape hatch?
Sure, please use unsafe_memcpy(), and include a comment on how the sizing
has been bounds checked, etc.
--
Kees Cook
next prev parent reply other threads:[~2023-10-02 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 5:25 [linux-next:master] BUILD REGRESSION df964ce9ef9fea10cf131bf6bad8658fde7956f6 kernel test robot
2023-09-30 5:25 ` kernel test robot
2023-09-30 5:25 ` [Intel-wired-lan] " kernel test robot
2023-09-30 5:25 ` kernel test robot
2023-09-30 21:56 ` Kees Cook
2023-10-02 3:22 ` Kent Overstreet
2023-10-02 4:52 ` Kees Cook [this message]
2023-10-03 13:27 ` Kent Overstreet
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=202310012150.72AAB06FAD@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
/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.